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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description adds real value by enumerating the payload: pricing, markets, custody model, sourced red flags, report card, and impostor scam reports — telling the agent this is a rich dossier rather than a stub.

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?

A single front-loaded sentence with zero filler; the resource and scoping are stated first and the payload enumeration is dense but 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?

For a read-only single-record lookup with annotations covering safety and no output schema, the description gives an adequate picture of what comes back. It stops short of edge-case behavior (e.g., unknown slug handling), which is minor.

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?

Only one parameter with 0% schema description coverage, so the description must carry the load. "By slug" identifies the key and ties it to list_bots, but gives no format or validation detail for the slug itself.

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?

States a specific verb+resource: retrieves a full fact sheet for a single bot identified by slug. Naming list_bots as the source of the slug helps separate it from siblings, though it doesn't contrast against check_bot or compare_bots directly.

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?

"(see list_bots)" implies the slug must first come from another tool, which is useful implied workflow. However it gives no explicit when-to-use-this vs check_bot guidance or exclusions, leaving the agent to infer the choice.

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