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

Annotations cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description doesn't need to restate that. It adds that the content is machine-readable and enumerates its categories, which is useful, but with no output schema it doesn't disclose the exact return shape (e.g. JSON structure, versioning). This is a safe read tool, so the remaining bar is low.

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 front-loaded sentence with no filler. It states the verb, the resource, and the enumerated contents efficiently.

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?

For a no-arg read tool, the description covers what the tool returns and that the content is machine-readable, which is what an agent needs to decide to call it. It would be slightly stronger if it named the companion write tool or noted the format for moves, but it is close to complete.

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?

Zero parameters, so the baseline is 4. The description carries no parameter burden, and the empty schema is fully consistent. Nothing is missing on this dimension.

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 names a specific verb and resource: reading Arena rules, difficulty levels, move formats, and limits. That is more precise than a bare 'get instructions' and distinguishes it from sibling tools like morrowkin_submit_arena_move. It is clear, though it doesn't explicitly call out its relationship to the other Arena tool.

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 use case is implied – an agent should read the rules and formats before acting – but there is no explicit when-to-use statement, no reference to morrowkin_submit_arena_move or how the returned formats must be applied. Adequate but leaves the agent to infer the workflow.

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