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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it returns text, supports cynical and corporate modes that alter answer weighting and style. This is consistent with the annotations and adds value beyond the structured fields.

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 three concise sentences with no filler. It front-loads the core function, then lists the optional modes, then gives usage guidance. Every sentence earns its place, making it efficient and well-structured.

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, non-destructive tool with an output schema present, the description covers everything an agent needs: what it does, when to use it, and the available modes. There are no missing details that would prevent correct invocation, and the output schema handles return format expectations.

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 input schema has 100% coverage with descriptions for all three parameters. The description mentions 'cynical mode' and 'corporate mode' which aligns with the boolean params, but the schema already explains them ('Weighted toward negative responses' and 'All answers in business speak'). Thus the description adds little semantic value beyond the schema, so a baseline 3 is appropriate.

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 clearly states the tool's function: 'Ask a yes-or-no question and get a mystical answer' and mentions it returns response text. It also distinguishes it from siblings by its playful nature (mystical, humorous), and the sibling list contains no similar random-answer tool, so there is no ambiguity.

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 explicitly provides usage scenarios: 'Use when you need a random decision, tie-breaker, or humorous perspective.' This is clear guidance, though it doesn't explicitly mention when not to use it or name alternative tools, but given its unique fun purpose, that is sufficient.

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