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

The annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds something the annotations do not: the required scope 'listings:read', which is genuinely useful for an agent planning a call. It doesn't need to explain the return payload since an output schema exists, so the remaining behavioral gap is minor.

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?

It is a single sentence with no filler paragraphs, which is appropriate for a one-parameter tool. But the parenthetical 'the listing earns what MakerRadar's badge earns (the answer says what)' is circular and confusing, and the earning detail is redundant given an output schema that presumably explains it.

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: one required parameter, full schema coverage, rich annotations, and an output schema. The description supplies purpose, intended placement, and the required auth scope, which is enough for correct invocation. Only the muddled earning explanation keeps it from being fully complete.

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?

There is a single required parameter and the schema documents it at 100% ('The listing's id.'). The description only implies the same thing via 'the listing's own website', adding no format, sourcing, or validation detail beyond the schema. Baseline 3 applies when the schema fully carries parameter meaning.

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 says concretely that this returns the HTML badge for the listing's own website, which is a specific resource tied to a specific listing. It is clearly distinct from sibling tools like get_my_listing or get_listing_options, though that distinction comes from the name rather than any explicit contrast. The clause about earning 'what MakerRadar's badge earns' is vague and defers the answer elsewhere.

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?

It gives an implied use case ('put it on the homepage'), which tells the agent the intended context for the returned snippet. However, there is no statement of when not to use it, no named alternative, and no guidance on whether the badge must be re-fetched if the listing changes. Usage is suggested rather than specified.

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