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

The description presents a plain enumeration ('List pools'), yet annotations declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false. A list operation described as read-style while flagged destructive is a direct inconsistency, and the description never reconciles it or explains the side effects.

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 five-word sentence with no filler and the scope front-loaded. It is efficient, though arguably too terse to carry the behavioral burden the missing annotations context requires.

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?

There is no output schema and no description of what a pool contains or what the listing returns, which matters for a list tool. Combined with the unexplained destructive annotation, an agent lacks enough to call this confidently.

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 100%, with stage_id and session_token both documented in the schema, so the baseline is 3. The description adds nothing about the parameters beyond restating the stage scoping already implied by the schema.

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 ('List') and resource ('pools') plus its scope ('in a stage'), so the operation is unambiguous. It does not differentiate from sibling list_* tools or explain what a pool is, but the core purpose is clear.

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?

No guidance on when to use this versus siblings like list_stages or get_stage, and no prerequisites stated. The only implicit cue is the 'in a stage' scoping, which the caller must infer.

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