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

Annotations already declare the read-only, non-destructive, open-world nature of the tool. The description adds valuable behavioral context by describing the return contents in detail (every delivered file with role, format, size, content hash, and labeled counts), which helps the agent understand what to expect. It does not mention pagination, rate limits, or authentication, so it is not fully comprehensive.

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?

The description is a single efficient sentence that front-loads the core purpose and then details the contents. The phrase 'counts that name the population each one counted' is slightly opaque, but overall there is no wasted material.

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?

Given the simple one-parameter read-only tool and the absence of an output schema, the description adequately explains what the inventory contains. However, it omits the meaning of listing_id and any guidance on when to choose this tool over sibling manifest tools, leaving meaningful gaps for correct invocation.

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 one required parameter (listing_id) with 0% schema description coverage, and the description does not mention it at all. It provides no clarification of whether listing_id refers to a bundle, asset, or listing identifier, leaving the parameter's exact meaning undocumented.

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 uses a specific verb ('Read') and a clear resource ('per-asset bundle inventory') and enumerates the fields returned (role, format, size, content hash, counts). It distinguishes itself from generic asset tools by emphasizing the bundle inventory, but it does not explicitly contrast with sibling tools like get_asset_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?

The description explains what the tool returns but gives no guidance on when to use it versus alternatives such as get_asset_manifest or get_agent_commerce_manifest. There are no exclusions, prerequisites, or usage conditions stated.

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