Classify text by its control function
Evaluate instruction text according to whether it defines a tool contract, routes a task or directs loaded behavior.
These examples and illustrative results are independently authored teaching materials, not measured model results.
Use case
Use this appears in skill metadata, tool schemas and loaded bodies, serving routing, contracts or behavior. Keyword blacklists cannot classify them.
Mechanism
Record consumer/loading stage/function/authority per field. Metadata states activation, tools define parameters/returns/limits and bodies supply workflow/reasons. Remove irrelevant promotion/steering from contracts while preserving precision. Render and verify moved text’s routing/calls without authority elevation. Length is not a universal criterion.
Bad example
Delete every MUST/Use this and call parameterless one-line tools improved.
Good example
Classify fields: retain scope triggers, precise tool parameters/exclusions and body behavior. Remove unrelated promotion, record assembled consumers and check routing rather than equating identical wording with function.
Why the change matters
Function follows loading boundaries, not tokens. Classification preserves necessary contracts and separates interface details from misplaced conversational steering.
Observable expectation
Teaching metadata distinguishes review/execution, returned fields stay accurate and workflows remain readable. Lost parameter explanations causing miscalls regress. Check authority/availability changes; unrun classification is static only.
Limits
Frozen model/sentence-count policies are not universal. Host authority boundaries vary and precision/brevity depend on interface complexity.