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

With no annotations, the description carries the full burden, and it does disclose one meaningful boundary: this tool returns inventory only, and binary payloads are not served here. It omits other behavioral traits an agent would want, such as read-only nature, whether the flow must already exist, and whether results are paginated or cached.

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 compact sentence with the outcome front-loaded and no filler; nothing is repeated from the name or schema. Density from terms like 'content-addressed' costs a little readability but there is no wasted text.

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?

No output schema and no annotations mean the description must explain the manifest's shape and the flow_id input, and it does neither. An agent knows the tool exists and that binaries come from REST, but not what a 'shard inventory' record contains or what identifier to supply.

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?

The single parameter flow_id has 0% schema description coverage and is not mentioned anywhere in the description, so its meaning and expected format are undocumented in both places. The sentence focuses on the return payload rather than the input needed to invoke the tool.

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?

Names a specific verb ('Discover') and resource ('BIS shard inventory') scoped as a manifest, which separates it from bis_observations and bis_records (data fetchers) among the siblings. The phrasing 'content-addressed BIS shard inventory' is jargon-heavy, so an agent gets the gist but not a crisp plain-language statement of what comes back.

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?

'binary shards remain REST downloads' implies the intended workflow: use this tool to discover the inventory, then fetch binaries out-of-band via REST. That is useful when-not guidance, but there is no explicit statement of when to pick this over the sibling bis_* tools or any prerequisites for making the call.

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