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

With no annotations, the description compensates by detailing the return content (name, tagline, price tiers, capability radar, etc.). However, it does not explicitly state that it's a read-only operation, which is a minor gap.

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 two sentences, front-loaded with the primary action, and includes essential return details. Every sentence adds value with no 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?

Given the tool has one parameter and no output schema, the description is highly complete. It lists the returned fields (name, tagline, pitch, etc.), mentions the 6-axis radar, knowledge topics, pairing bots, and team synergy bonuses, and references sibling tools for slug discovery.

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% for the single parameter (slug). The description mentions slugs can be found via sibling tools but adds no new semantic detail beyond the schema's description. The schema already provides examples, so the description's contribution is minimal.

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 retrieves the full card for a bot by slug, with a specific verb ('Get') and resource ('full card for one URBot bot'). It distinguishes from siblings by mentioning how to find slugs via list_bots or search_bots.

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 explicitly tells when to use this tool: when you have a slug to get a bot's full card. It also directs users to sibling tools (list_bots, search_bots) for finding slugs, providing clear context for when not to use this tool.

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