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

Annotations already provide readOnlyHint=true, and the description's 'Read' is consistent. It adds useful content context about D-269 v1 capability badges and commercial terms, but it does not describe return shape, access requirements, or other behavioral details.

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 front-loaded sentence with no filler; the title reinforces the purpose. The 'D-269 v1' parenthetical is somewhat cryptic but compact and does not waste space.

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?

Adequate for a simple one-parameter read operation with readOnlyHint, but with no output schema the agent is left to infer the manifest's exact return structure. It also lacks routing guidance among the sibling manifest tools.

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 echoes 'for a listing' rather than explaining the listing_id parameter's semantics. The single UUID parameter is fairly self-explanatory from its name, but the description adds little beyond the schema.

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 ('Read') and resource ('agent commerce manifest for a listing'), with the title clarifying that the resource is 'a listing's commercial terms'. The listing scope plus 'D-269 v1 capability badges' distinguishes it from sibling manifests like get_asset_manifest and get_bundle_manifest.

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?

Implies use when the caller needs the commercial terms or capability badges for a specific listing. It does not explicitly contrast with get_asset_manifest or get_bundle_manifest, nor say when not to use it.

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