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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses that nothing is created or deleted, and the page will never be proposed again. It also clarifies how mis-filed pages can be moved, reducing decision anxiety. No contradiction with annotations.

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 moderately long but every sentence earns its place by clarifying usage, behavior, or alternatives. It is front-loaded with the primary action and then expands logically. Could be slightly tightened but no wasted words.

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 dismissal tool, the description fully covers what it does, when to use it, what it doesn't do, and how to handle related scenarios (accepting, converting). An output schema is absent, but the description makes the tool's effect clear enough without needing return-value details.

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 schema already covers both parameters with descriptions (100% coverage), but the description adds practical sourcing guidance: url should be exactly as list_corroboration_candidates provides it, and project_id is a UUID from list_projects. This extra context elevates beyond baseline.

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 refutes a suggested page, permanently removing it from future proposals for the project. It gives specific usage criteria and distinguishes it from accepting by pointing to create_corroboration and create_surface as opposite moves.

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?

Provides explicit when-to-use conditions (excerpt matched something else or page not worth recording) and when-not-to-use with explicit alternatives (create_corroboration, create_surface, convert_corroboration_to_surface, convert_surface_to_corroboration). This is exemplary guidance.

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