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

Annotations already declare the full safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description earns credit by disclosing what each mode returns (six questions vs. tilt plus short explanation), which is genuinely useful since there is no output schema; it does not mention answer-count validation or pagination-style concerns, but for a read-only quiz that is minor.

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?

Two tight sentences, each covering one mode, with the no-answers case front-loaded. No filler, no repetition of the title.

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, read-only quiz with no output schema, the description covers both the input expectation and the return shape adequately. It could go slightly further on what the 'tilt' categories mean or how many answers are expected, but nothing critical for correct invocation 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?

Schema description coverage is 100% and the single optional parameter is already documented ('One tilt per question') with its enum values in the schema. The description restates the enum ('chaser, inventor, reader') and the per-question cardinality, adding little beyond structured data, so the 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?

The description states a specific behavior with two clear modes: returning six quiz questions when called without answers, and returning a computed 'tilt' plus explanation when called with answers. This is a precise verb+resource statement, though it does not explicitly distinguish itself from the sibling 'viral_attention_patterns', which an agent might reasonably confuse it with.

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 clearly defines the two invocation conditions ('Without answers...' vs 'With answers...'), which tells the agent exactly when each code path applies. It stops short of naming alternatives or stating exclusions relative to sibling quiz/scoring tools, so it is clear context rather than full routing guidance.

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