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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond them: an authentication requirement ('Requires a token') and an explicit statement of what side effects are NOT performed, which is exactly the kind of added value annotations cannot express.

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 tightly packed sentences, front-loaded with the core action and contents, followed by a scope disclaimer. No filler or redundancy.

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 two-parameter, read-only, no-output-schema preparation tool, the definition covers the action, brief contents, auth requirement and negative scope. What it does not address is what the brief returns or how it differs specifically from list_verification_tasks, leaving a small gap.

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 50%: api_key is documented in-schema, while task_id carries only a pattern with no prose. The description's 'Requires a token' reinforces the api_key semantics but adds nothing about task_id, so it neither compensates for the gap nor drops below the schema-coverage baseline of 3.

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 gives a specific verb+resource ('Prepare a verification brief') and enumerates the brief's contents (existing records, source starting points, evidence criteria), which is more informative than the bare tool name. It does not explicitly name a sibling to distinguish itself from, so it stops 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?

'No external research, task reservation or publication is performed' establishes clear scope boundaries that implicitly route agents away from call_research_tool and publish_information. It gives when-it-fits context but never names the alternative tools explicitly, so it is not a full 5.

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