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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds that results are 'bounded' and that complete transfer should use the manifest/shard path, but it does not explain pagination behavior or what bounded means in practice.

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 front-loaded sentence with no wasted text. It is concise and immediately communicates the browsing scope plus the complete-transfer alternative.

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?

With no output schema and no parameter descriptions, the definition leaves important operational details unspecified: what BIS records contain, how pagination via cursor works, and how limit affects results. The manifest alternative helps, but the tool is still under-described for its three-parameter interface.

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%, so the description needs to compensate for undocumented parameters. It weakly implies bounded results through 'bounded' but does not explain flow_id, limit, or cursor semantics.

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 states a specific verb and resource: browsing bounded BIS records. It also hints at the distinction from complete transfer via the flow manifest and shard URLs, though the domain-specific BIS terminology and 'full-fidelity' wording remain somewhat opaque.

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?

It gives a clear use case for browsing bounded records and explicitly points to the flow manifest and shard URLs for complete transfer. That provides a meaningful alternative path, though it does not fully contrast with siblings like bis_observations.

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