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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's remaining burden is interpretability, and it delivers: it warns that positioning flagged written_by "vendor" is a company claim rather than a directory finding. It does not cover error behavior for an unknown slug or data freshness beyond 'last checked'.

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?

Two sentences, front-loaded with the payload description and closing with the one interpretive caveat that matters. The field list is dense but each item is concrete; nothing is padding, though the first sentence runs long as an enumeration.

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?

With no output schema, the description carries the return-shape burden and does so by enumerating the fields (identity, location, licensing, price, last-checked, review count/average, positioning). An agent can call this correctly and interpret the result; only error/failure behavior is unaddressed.

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 100% and there is a single required parameter with its length bounds and sourcing instructions already in the schema. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 states a specific verb (read) and resource (one listing) and enumerates the returned fields, so the agent knows exactly what this tool produces. It does not explicitly name the sibling tools it competes with, but 'one listing' versus search/compare/list is clear from the name and title.

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?

Usage is only implied: fetch detail once you already have a listing identity. The slug parameter description does route the agent to search_tools or find_alternatives as sources for the slug, which is useful indirect guidance, but there is no explicit when-to-use versus when-to-prefer-compare_tools or find_alternatives.

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