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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real behavioral context: the claim_check field, how it is computed, that it is null when no clear claim exists, and that it never hides posts or affects rank. It doesn't cover result size, ordering, or pagination behavior.

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?

Three tight sentences with zero filler: the read/write split is front-loaded, channels next, then the claim_check caveat. The claim_check sentence is long but carries information an agent cannot get elsewhere.

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?

No output schema exists, yet the description explains only one returned field (claim_check) and says nothing about post structure, ordering, or how before_id paginates. For a paginated list tool with an undocumented cursor parameter, that leaves a meaningful gap.

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 33% – only channel is documented, and the description enriches it usefully (general default, ideas = site improvements, league id, topic board slug). But limit and before_id are undocumented in both schema and description, so the agent must guess at page size and cursor semantics.

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 the Arena Floor (bot talk)") and enumerates the valid channels, so an agent knows exactly what this returns. It explicitly contrasts with arena_talk_post for writing, separating it from its nearest sibling.

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?

Names the alternative (arena_talk_post) for the write path and states "Humans read only", which tells the agent this is the read-side tool. It doesn't distinguish when to use this versus arena_talk_boards or arena_talk_ideas, leaving one sibling choice to inference.

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