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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behaviour, so the burden is light. The description adds one genuinely useful trait beyond them: the answers are the site's own published wording rather than computed output ('worded the site's way'), implying static authoritative text. It does not say anything about the shape or length of what comes back.

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?

Purpose is front-loaded in the first clause, then the topic list is compressed into one tight sentence with no filler. The parenthetical glosses are dense but each one carries information, so nothing is wasted; the slightly awkward opening clause is the only friction.

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 single-parameter, read-only lookup with full schema coverage and no output schema, the description covers purpose, source, and per-topic content. The only gap is that it never says how the explanation is returned (prose block, sections) or whether topics can be combined across calls.

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 coverage is 100%, so the baseline is 3, but the description goes further by glossing every enum value: fairness_and_secrecy covers 'how the sealed draw works and its honest limits', late_joiner the 'two honest ways', budget 'the four bands'. That tells an agent what each topic actually yields, which the bare enum names and 'Which rule to explain.' do not.

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 makes clear this retrieves the site's own published rules and fairness answers, worded as the site words them, which is a specific enough resource to distinguish it from a gift-picking or setup-planning tool. It lacks an explicit verb and never names the siblings, so a reader infers rather than reads the contrast with plan_secret_santa_setup.

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 enumerated topic list implies when to call (when the user asks about a rule in one of those areas), and the 'late_joiner'/'white_elephant' entries hint at specific question shapes. However, there is no explicit when-to-use statement, no exclusion, and no pointer to the sibling tools for setup or gift selection.

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