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

Adds genuinely useful behavior beyond the annotations: pricing ($0.01/call, first 25 free, failed calls free) and the fact that repeat calls are charged, which explains idempotentHint=false. 'Reads or computes only and changes nothing' largely restates readOnlyHint, but the cost and randomness disclosure carry real value.

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?

Front-loaded with purpose, usage, example, and pricing in a compact block. The sentence 'Reads or computes only and changes nothing' is redundant with the readOnlyHint annotation, a minor waste.

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 one-optional-parameter novelty tool with no output schema, the description covers purpose, random output, cost model, and intended audience. It could be stronger by pointing at yes_no for a deterministic alternative, but nothing essential for calling it correctly is missing.

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?

With 100% schema coverage and a single optional 'question' parameter, the schema already does the documentation work. The example (question=Will it ship today?) clarifies expected format but adds little beyond what the schema states, so baseline 3 applies.

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 ('ask a yes-or-no question and get one of the 20 classic Magic 8-Ball answers, chosen at random'), which is clear and unambiguous. It does not differentiate from the sibling 'yes_no' tool, which is the nearest alternative, so it falls short of a 5.

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?

Gives explicit use context ('For fun only. Use for games and chat bots'), which is more than implied usage. It does not name exclusions or the sibling alternative yes_no for deterministic answers, so no 5.

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