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

Annotations already declare this a safe, idempotent read, so the description's value is the paging contract: long bubbles arrive in 30000-character pages and the reply ends with the offset to read next. That is a genuinely non-obvious behavioral trait an agent must know to avoid treating a truncated page as the full content. It stops short of covering error handling or what the 'short header' contains.

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?

Two sentences, zero waste, and the identifier-plus-return-shape is front-loaded ahead of the pagination caveat. Every clause carries information an agent needs.

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, the description must convey return shape, and it does: header, Markdown body, and a trailing next-offset. Pagination — the one thing most likely to cause a silent correctness bug — is covered. The vague 'short header' and the absence of any note on missing/invalid ids keep it from a 5.

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 coverage is 100%, with per-parameter descriptions for id, offset, and max_chars, so the schema already does the heavy lifting. The description reinforces the offset/max_chars interplay by explaining the 30000-character default and continuation offsets, but adds no syntax or constraints beyond the schema. Baseline 3 is appropriate.

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 specific verb and resource — 'Read one Sixteen Bridges bubble' — and describes what comes back: a short header followed by Markdown content. 'One' explicitly distinguishes it from the sibling sixteenbridges_list_bubbles, so an agent can route correctly without opening a schema.

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 single-object framing implies usage (fetch a specific bubble by id), but the description never says when to prefer this over list_bubbles, nor when to continue paging versus re-reading. The routing hint it does provide lives in the schema ('From sixteenbridges_list_bubbles'), not the description.

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