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

Annotations declare the safety profile (destructive, non-idempotent, not read-only), and the description adds substantial context beyond them: stale versions are refused, there is no legacy fallback, stop does not mean drained and quiescence must be re-checked, and the browser requires human approval because ongoing acquisition changes. This is rich behavioral disclosure that complements rather than repeats the annotations.

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 action statement is front-loaded and every sentence is substantive, but the browser-approval point is made twice ('the browser reads and binds this version during approval' and 'the browser requires the person's approval'), which adds minor redundancy to an otherwise tight description.

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?

Although there is no output schema, the description states the return values (new bounded state and version), the required pre-step, the failure mode for stale versions, the meaning of stop, and the human-approval gate. Nothing material for correct invocation is missing.

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 carry parameter meaning, and it does explain expected_version's provenance and error behavior (stale version refused). subscription_id is only implied by 'one subscription' and the action options are covered by the title/enum, so it partially but not fully compensates for the missing schema documentation.

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 opens with a specific verb set (pause, resume or stop) and a precise resource (one subscription), and the mechanism named (bounded quiescence CAS API) further distinguishes it from siblings like get_stream or start_stream. An agent can identify this as the mutating control tool without opening the 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?

It states a concrete prerequisite workflow: call get_stream kind quiescence first and pass its version as expected_version, and explicitly rules out fallback to 'legacy unfenced actions'. It does not, however, explain when to prefer pause vs resume vs stop beyond the enum itself, so it stops short of full alternative routing.

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