botindex_discover

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the tool is 'FREE' which hints at pricing, but doesn't describe authentication requirements, rate limits, response format, pagination, or what 'full' means in terms of completeness. For a catalog tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise (one sentence) with zero wasted words. It's front-loaded with the core purpose and includes only essential additional context ('FREE'). Every element earns its place.

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 has no parameters (schema coverage 100%) and no output schema, the description adequately covers the basic purpose. However, for a catalog/discovery tool that presumably returns structured data about APIs, the description should ideally mention what format the catalog is returned in or how to interpret results. The 'FREE' mention adds some context but doesn't fully compensate for the lack of output information.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents the empty parameter set.

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 action ('Get') and resource ('full BotIndex API catalog') with specific details about what it includes (endpoints, pricing, descriptions). It distinguishes itself from siblings by being a catalog/discovery tool rather than specific data retrieval functions, though it doesn't explicitly name alternatives.

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 provides no guidance on when to use this tool versus the many sibling tools. While it implies this is for discovering available endpoints, it doesn't specify use cases, prerequisites, or exclusions. The 'FREE' mention hints at cost but doesn't provide meaningful usage context.

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