search_skills

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

Describes ranking, included fields, and language support. Does not explicitly state it's read-only but infers from context. Lacking annotation coverage, description carries full burden and does well but misses explicit non-mutation statement.

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?

Concise 4-sentence description front-loaded with purpose. Every sentence adds distinct value without 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?

Fully explains result fields and next step. No output schema, but description sufficiently covers what to expect. Sibling tools are indirectly addressed via linkage to get_skill.

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 baseline 3. Description adds query examples and limit defaults/maximum, enhancing usability beyond schema.

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?

Clearly states the verb 'Search', the specific resource 'BytesAgain index of 60,000+ AI agent skills', and distinguishes from sibling tools like get_skill (detail retrieval) and popular_skills (ranking list).

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?

Explicit instructs to use when user asks for tools, agents, etc. for a specific job. Provides supported languages and a clear post-search action (call get_skill with slug).

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