search_skills

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

With no annotations, the description carries the full behavioral transparency burden. It mentions the external source (skills.sh) but does not disclose return format, pagination, rate limits, or whether results are ordered. The agent has no information about what a successful response looks like or any side effects.

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, front-loaded with the action 'Search for skills', and every word adds meaning. No filler or redundant information.

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?

The tool is simple with two parameters, and the description covers its core purpose. However, since there is no output schema, the description should ideally mention what the search returns (e.g., a list of skill names) to fully prepare an agent. This is a notable gap, but the tool's straightforward nature keeps it at a minimal viable level.

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?

The input schema already describes both parameters (query and limit), and the description adds value by providing example query terms that clarify the expected input format. This goes beyond the schema's generic 'Search query term' description.

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 clearly states the tool searches for skills on skills.sh using a query term, and includes concrete examples (mapbox, react, gis). This distinguishes it from sibling tools like get_skill_details and get_popular_skills, which perform different operations.

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 for finding skills by term, but it does not provide explicit guidance on when to prefer this tool over siblings or when not to use it. No alternatives or exclusions are mentioned, leaving the agent to infer context.

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