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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, openWorldHint=false), so the bar is lower. With no output schema present, the description usefully discloses the response payload — verdict, strength and rationale, alternatives with group advice, risks, and required gates — which the agent could not otherwise infer.

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?

A single dense sentence that front-loads the subject ('For one ... item') before listing outputs. It is long but every clause earns its place by naming a distinct part of the answer; only the item-type enumeration is slightly padded.

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 read-only tool with no output schema, the description enumerates the return contents and the possible verdicts, and the schema fully documents the nested context. Nothing critical is missing for correct invocation, though the tool's relationship to siblings like check_gate and explain_node is left to inference.

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% with three parameters, including the deeply documented nested context object, so the schema already carries the parameter semantics. The description only echoes 'this context' without adding format, defaults, or examples beyond what the schema provides, making the baseline 3 correct.

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 action (evaluate whether one item fits a context) and enumerates the item types it covers (event, practice, technique, notation, tool, artifact, antipattern) plus the verdict vocabulary (fits/avoid/not_applicable/antipattern). An agent can tell it apart from validate_plan or check_gate, though the sibling differentiation is implicit rather than explicit.

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 'For one ... item' framing implies the per-item scope and 'which gates require it' hints at the relationship to check_gate, but there is no explicit statement of when to choose this over explain_node, search_graph or check_mix, and no exclusions or prerequisites are given.

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