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

No annotations are provided, so the description carries the full disclosure burden. 'Read' weakly implies a safe read operation and 'bounded' hints at a result cap, but 'revision-aware' is never explained, and nothing is said about permissions, pagination, rate limits, or what a revision-aware read actually returns.

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?

It is a single front-loaded sentence with no wasted words, which is structurally clean. The terseness, however, reads as under-specification rather than disciplined concision given the total absence of supporting detail.

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, no annotations, and zero parameter documentation, the description needs to explain the return shape, the meaning of revision-awareness, and how to supply a flow_id. None of that is present, leaving the agent materially under-informed for a tool with a required identifier parameter.

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 must compensate and does not. 'flow_id' is never explained (what a flow is, its format, where to obtain it), and 'limit' is only obliquely referenced by the word 'bounded' rather than tied to the 1-1000 range or default behavior.

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 (Read) and resource (BIS observations), which is better than a tautology. However, the modifiers 'bounded' and 'revision-aware' are unexplained jargon, and it gives no signal to distinguish this from siblings like bis_records or seiche_observations.

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?

There is no guidance on when to use this tool versus bis_records, bis_flow_manifest, or seiche_observations, and no prerequisites or exclusion conditions are stated. The agent is left to infer everything from the name alone.

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