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

With no annotations, the description carries the full burden and delivers a useful non-obvious behavioral detail: sold units return status 'sold' and price null. This is exactly the kind of quirk-wise context that helps an agent interpret results. It lacks error/not-found behavior and auth notes, keeping it below 5.

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 tight sentences, front-loaded with the primary action, the second sentence adding high-value edge-case info. Zero waste.

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-param read tool with no annotations or output schema, the description supplies the key domain quirk (sold → null price). It would be fully complete with a note on not-found behavior or id source, but it's largely sufficient.

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?

One parameter with 0% schema description coverage. The description implies listing_id identifies the listing but adds no format or provenance detail (where the id comes from, expected shape) beyond the name. Baseline for a single param with full context would be higher; here it's marginal.

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 specific verb ('Get') and resource ('one Track & Blade listing by listing_id'), identifying the singular-lookup nature that distinguishes it from the plural sibling search_listings. The resource bounding is clear.

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?

No explicit when-to-use guidance or reference to alternatives. The 'one ... by listing_id' phrasing implicitly signals single-item retrieval versus search_listings, but no condition or exclusion is stated.

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