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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, lowering the bar. The description adds value by disclosing what the response contains (price, rights, how to buy), but says nothing about failure modes for an unknown listing_id or what 'rights' means structurally.

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?

One short sentence, front-loaded with the verb and resource, with the highest-value detail (the returned fields) placed immediately after. No filler.

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 single-parameter read tool with annotations covering its safety profile and no output schema, the description supplies the essential payload summary. The only meaningful omission is identification of the argument as a listing UUID and any error expectation.

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% for the single listing_id parameter, and the format is uuid. The description only says 'for a listing', without explaining that the argument is a listing UUID or how to obtain one, so it does not compensate for the schema gap.

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 and resource ("Read the agent commerce manifest for a listing") and enumerates the payload (price, rights, how to buy). It is clearly not get_asset_manifest or get_bundle_manifest by virtue of the commerce framing, though it never names those siblings to make the distinction explicit.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives among fetch, get_asset_manifest, get_bundle_manifest, or search_assets. Usage is only inferable from the payload description.

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