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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the manifest is 'canonical' and 'sha256-stamped', which hints at integrity guarantees on the returned content, but says nothing about failure modes, staleness, or what a manifest actually contains.

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?

It is a single short sentence with the key qualifiers up front and no wasted words. However, the terseness crosses into under-specification: the whole budget is spent on adjectives rather than on the usage and parameter context the tool lacks.

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 one-parameter read with no output schema, the description should at minimum explain what the manifest is and what listing_id identifies. Instead it leaves the return shape, the meaning of 'canonical', and the id semantics unaddressed, so an agent knows the safety profile but not the contract.

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?

There is a single required parameter, listing_id (uuid), and schema description coverage is 0%, so the schema supplies only the type and format. The description never mentions listing_id, its provenance, or whether an unknown id errors versus returns empty — the parameter is entirely undocumented at the semantic level.

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 ('asset manifest'), with the qualifiers 'canonical' and 'sha256-stamped' that narrow the meaning. It implicitly distinguishes from get_bundle_manifest by naming 'asset' rather than 'bundle', but never makes that contrast explicit against the several manifest-related siblings.

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 guidance at all, and despite siblings like get_asset, get_bundle_manifest, get_agent_commerce_manifest and search_assets, the description names no alternative or exclusion condition. The agent must infer the selection criteria from the tool name alone.

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