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

Annotations already mark this as read-only, so the description doesn't need to cover safety. It adds useful behavioral context by noting the result is random and that it 'Returns a labeled strategy card,' which goes beyond what the annotations specify. No contradiction with 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 description is short and front-loaded with the core purpose. It is slightly repetitive, restating the 'use this when' guidance twice, but every part is otherwise useful and the overall length is appropriate.

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 simple, read-only, zero-parameter tool, the description covers what it does, when to use it, and what it returns. There is no output schema, so the 'labeled strategy card' mention helps set expectations, though the exact card structure is not described.

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?

The tool has zero parameters and schema coverage is 100%, so there are no parameter details to document. The description appropriately implies no input is needed by saying 'Get a random' strategy, which is the expected baseline for a parameterless tool.

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 and resource: 'Get a random Pause strategy.' The 'Pause' category clearly distinguishes it from sibling tools like get-sideways-strategy-category-disrupt or reframe, without needing to open their schemas.

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 gives explicit use cases: 'when rushing, feeling frantic, or unable to see the forest for the trees' and 'rest, reflect, step back, examine, take breaks.' It does not explicitly name sibling alternatives or state when not to use them, but the context is clear enough for an agent to route correctly.

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