search_apis

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

No annotations provided, so description carries full burden. It mentions return content (names, descriptions, tags, etc.) but does not disclose whether it is read-only, auth requirements, rate limits, or order of results. Adequate but could be more explicit.

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 plus a usage tip. Front-loaded with purpose and output, followed by a clear instruction. No unnecessary words.

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?

No output schema, but description lists what is returned. For a search tool, it is fairly complete. Could optionally mention pagination or sorting, but not required. Sibling tools are diverse, so no further differentiation needed.

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%, but description adds value: it explains that calling without arguments lists all APIs and suggests using that to see available tags for the tag parameter. This guidance goes beyond the 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 it searches the API marketplace and returns a list of APIs. The verb 'search' and resource 'bolthub API marketplace' are specific. Among siblings, it is the only discovery tool, distinguishing it from tools like call_api or buy_credit.

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 says 'Use this to discover APIs' and provides an actionable tip: 'Call without arguments to list all available APIs.' Does not mention when not to use, but in context of siblings, it is clear that this is for discovery only.

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