find_skill

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true, so the safety profile is already covered. The description adds valuable context by indicating this is a pre-execution discovery step ('Use this before run_skill') and that the skill must be 'App-managed', but it does not describe output format or behavior when no skill is found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and resource; the second sentence provides actionable sequencing guidance. Every word earns its place, with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, annotations, and high schema coverage, the description provides enough context for a discovery tool: it states what it finds, for whom, and when to use it. The lack of output schema is partially mitigated by the clear relationship to run_skill, but a brief mention of the return value (e.g., skill ID) would make it fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86% with descriptions for mode, scope, intent, capability, and outputCapability, so the baseline is 3. The description adds minimal parameter nuance beyond linking 'intent' to 'user intent' in the usage sentence, so it does not exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the verb 'Find' with the resource 'App-managed skill' and scopes it to 'the current task', clearly stating its function. It differentiates from sibling run_skill by positioning this as a lookup step: 'Use this before run_skill'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to use this before run_skill, and specifies the condition: 'when the user intent requires a specialized App skill.' This provides clear when-to-use guidance and points to the alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.