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

The description says 'List', which signals a passive read, while the annotations declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false. That is a direct contradiction of the safety profile an agent would infer from the wording, with no explanation of what is actually modified or destroyed.

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 sentence with zero filler and the resource front-loaded. It is efficient, though arguably under-specified rather than optimally sized given the tool's unknowns.

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, two required parameters, and annotations describing a destructive, non-idempotent, open-world operation — yet the description explains none of this. An agent cannot tell whether calling this is safe, whether it needs write auth, or what it returns.

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%, so both pool_id and session_token are already documented in the schema; the description adds no syntax, format, or relationship detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ('standings for a pool'), which is clearly distinct from siblings like list_pools, list_stages, and list_entries. It does not, however, explicitly differentiate itself from the other read/listing tools beyond naming the resource.

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 when-to-use guidance, no prerequisites, and no pointer to alternatives (e.g., get_stage_table, list_pools) despite a dense set of sibling tools. The agent must infer that this belongs to the tournament/pool workflow from the schema alone.

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