find_skills

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

No annotations are provided, so the description carries the burden. It indicates a search operation (presumably read-only) and hints at the pagination parameters from the schema, but does not disclose any behavioral traits like authentication needs, rate limits, or whether the search is case-sensitive. Adequate but not thorough.

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?

The description is a single concise sentence that efficiently communicates the tool's purpose and a key usage hint. No unnecessary words, but could be slightly more structured with bullet points or additional context.

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?

Given the tool's simplicity (3 parameters, no output schema, no annotations), the description is minimally complete. It explains the purpose and a key mapping, but lacks details on return format, error handling, or behavior when no results are found. Adequate for a simple search tool but could improve.

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 100%, so the schema already documents all three parameters (query, page, limit) with descriptions. The tool description adds no extra meaning beyond confirming that query matches skill names. Baseline 3 is appropriate.

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 a clear verb 'Search' and resource 'global skill catalog'. It also adds context by mentioning that returned IDs map to 'skill_ids' on candidate search, which differentiates it from similar find tools like find_companies or find_locations.

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?

The description implies usage by linking skill IDs to candidate search, but it does not explicitly state when to use this tool versus alternatives or provide exclusions. No guidance on prerequisites or when not to use it.

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