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

No annotations are provided, so the description carries the full burden. It does disclose one meaningful behavioral trait beyond the schema: results are "bounded" and complete data requires the manifest/shard path. It omits pagination mechanics, permissions, and what "bounded" concretely means, leaving significant gaps for a no-annotation tool.

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?

A single front-loaded sentence with no padding; the browse action comes first and the alternative path second. It is dense with unexplained terminology, but nothing is wasted.

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, so the description must carry the full load, and it does not: pagination behavior, record contents, auth needs, and the meaning of flow_id/limit/cursor are all unaddressed. For a three-parameter data-retrieval tool, this leaves the agent under-equipped to invoke it correctly.

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% across three parameters (flow_id, limit, cursor). The description only loosely implies bounding, which weakly maps to limit/cursor, and says nothing about what flow_id identifies. With the schema silent and the description not compensating, the agent must guess at all three parameters.

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 verb ("Browse") and a resource ("BIS records") and qualifies it as "bounded" and "full-fidelity", which hints at how it differs from bis_observations and the manifest tool. However, "BIS" and "full-fidelity" are undefined jargon, so the agent cannot fully tell what record type this returns versus its 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?

The clause "use the flow manifest and shard URLs for complete transfer" effectively says when not to use this tool, routing the agent to the bis_flow_manifest sibling for full transfers. It gives clear context for the bounded-browse case, though it does not name the sibling tool explicitly or state prerequisites like a valid flow_id.

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