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

Beyond the annotations' read-only, non-destructive safety profile, the description discloses the capped wins and flags and the deliberate omission of the underlying score to discourage gaming. This is useful behavioral context, though it says nothing about the grading criteria or whether the grade can change as listing data changes.

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 compact and front-loaded with the tool's output, then efficiently covers audiences, an example request, and the important score limitation. Each sentence contributes distinct information without unnecessary wording.

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 one-parameter read operation with an output schema, the description supplies enough information to understand and generally invoke the tool correctly. Its main remaining gaps are slug acquisition or format and limited guidance about grading criteria or sibling-tool selection.

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 only says to "provide the slug." That confirms which input to supply but adds no slug format, example value, or guidance on obtaining it from another listing tool.

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 identifies the resource and result: a categorical quality grade for a Cyclesite listing, accompanied by up to two wins and two flags. The categorical-versus-numeric distinction clarifies its scope, although it does not explicitly differentiate the tool from siblings such as get_listing_detail or check_stolen.

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 two concrete use cases—buyer trustworthiness assessment and seller self-audit—and includes an example buyer question with the required invocation input. It does not name alternative tools for raw listing details, theft checks, or numerical valuations.

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