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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is fully covered. The description adds 'bounded' (implying the limit cap) and 'revision-aware', but the latter is never explained and there is no revision parameter in the schema, leaving the agent guessing what revision-awareness implies for results.

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 short phrase with no filler, so it is not bloated. But it is under-specified rather than concise—terseness here costs clarity rather than saving an agent anything.

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, no annotations gaps covered by prose, and undocumented parameters leave the definition thin. For a data-retrieval tool with a required flow_id and pagination-like limit, the description should at minimum say what is returned and how the flow scopes results.

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?

With 0% schema description coverage and two parameters, the description must carry the load: it never mentions flow_id as a required flow selector, nor explains limit semantics beyond the vague word 'bounded'. The agent must infer both parameters from names alone.

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 verb (read) and resource (BIS observations) with qualifiers 'bounded' and 'revision-aware', so the basic operation is inferable. But it offers no differentiation from close siblings like bis_records or seiche_observations, and 'revision-aware' is undefined jargon that doesn't help the agent distinguish use cases.

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 choose this over bis_records, bis_flow_manifest, or seiche_observations. There are no stated preconditions, exclusions, or alternative routes despite the crowded sibling set.

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