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

Annotations already declare the operation as read-only and non-destructive, so the description doesn't need to repeat that. It adds the output format (Markdown and HTML) but does not disclose other behavioral details such as required authentication, potential errors, or whether the badge status affects the snippet. No contradiction with annotations.

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 a single, front-loaded sentence with no filler words. It states the action and the deliverable directly, making it easy to scan.

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?

The tool is simple with one parameter and annotations cover side effects, so the description is mostly adequate. However, the lack of any parameter clarification and the absence of an output schema leave a notable gap for an agent trying to construct a correct call.

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% and the description does not explain what 'handle' means or how it should be supplied. The name suggests an identifier for the badge, but an agent would have to infer whether it's a username, badge ID, or slug, and no format or example is provided.

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 uses a specific verb ('Return') and identifies a concrete deliverable ('ready-to-paste Markdown and HTML for a live Chapa badge'), making the tool's function immediately clear. It is clearly distinct from sibling tools like verify_badge or get_impact_profile, which serve different purposes.

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 implies the usage scenario (need to embed a live Chapa badge) but does not explicitly state when to prefer this tool over alternatives or mention any exclusions. There is no direct comparison to sibling tools, though the specific phrasing gives some contextual signal.

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