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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat safety traits. It adds valuable context: the tool credits the creator X post, includes votes and adds, does not test/score/review bots, and never returns prompt text. This goes beyond annotations to set expectations about content, which is especially useful given no output schema.

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 three sentences, each adding distinct value: purpose, return details with social credit, and explicit exclusions. Information is front-loaded with the core action first, and there is no redundancy or filler. Every sentence 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 simple single-parameter read operation with rich annotations, the description is complete. It covers what the tool returns (listing with votes/adds), what the tool does (credits creator), what it does not do (test/score/review), and a critical exclusion (never returns prompt text). The lack of an output schema is compensated by the description's clarity on content. An agent has everything needed to call it correctly.

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 description coverage is 0%, so the description must compensate. The description uses 'by slug' to explain the slug parameter's purpose, adding meaning beyond the bare schema definition. It does not specify the slug format or constraints, but for a single required parameter, the description provides adequate semantic context.

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 precise action (fetch one public listing) with a clear resource (by slug), and adds distinguishing detail about crediting the creator X post and carrying votes/adds. The sibling tools like list_categories and search_bots are clearly different, so there is no ambiguity.

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 clearly implies when to use this tool: when a specific public listing by slug is needed, as opposed to browsing categories or searching. It does not explicitly name alternatives, but the context signals of sibling tools make the use case clear. A minor gap is not explicitly stating when not to use it (e.g., if you need to search), but the single-listing focus is evident.

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