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

The readOnlyHint annotation already establishes that this is a read-only operation, and the description is consistent with that. It adds useful context by describing what the returned inventory contains, but it does not disclose potential failure modes, access requirements, or other behavioral nuances.

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 focused sentence that front-loads the action and resource before listing the relevant output fields. It is concise and mostly free of filler, though the phrase 'counts that name the population each one counted' is slightly awkward and could be clearer.

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-parameter read-only tool, the description conveys the primary output contents and is mostly sufficient. However, it leaves the meaning of listing_id implicit and does not address how this tool relates to the sibling manifest and asset tools, so an agent may lack enough context to invoke it correctly in a complex workflow.

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 only one required parameter, listing_id, and the schema provides no description for it. The tool description does not clarify what listing_id refers to or how it relates to the bundle, leaving the agent to infer that it identifies the bundle/listing. With 0% schema description coverage, the description should have compensated more.

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 clearly states a read operation on a bundle inventory and lists the specific returned fields: role, format, size, content hash, and counts. It is specific enough about what the tool does, though it does not explicitly differentiate itself from sibling tools like get_asset_manifest or get_agent_commerce_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 gives no guidance on when to prefer this tool over its siblings or when not to use it. The intended use is implied by the name and wording, but the agent is left without explicit context for choosing between similar manifest-related tools.

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