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 the actual side effect profile: it is recorded as a signal for desk review and counted per page, but 'does not mark the page verified, change its date or reorder any list, and the page itself does not change.' It also explains the refusal conditions and confirms idempotency in plain language ('The same confirmation sent twice is recorded once'), which is exactly the kind of context annotations cannot carry.

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 definition is dense and front-loads the core action, then layers trigger, alternative, validation rules, and side effects in a logical order. Most sentences earn their place, though the closing 'Returns whether it was recorded' is partly redundant given the output schema, and the middle clauses pack many constraints into single sentences.

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?

With an output schema present, the description only needs to name the return ('Returns whether it was recorded'), which it does. Combined with the annotations and full schema coverage, an agent has everything needed: trigger, alternative, validation rules, and the exact (non-)effects of the call.

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%, so the baseline is 3; the description still adds meaning by demanding checked_text be quoted 'exactly as the page (or this server's answer) gives it' and by stating the consequences for a non-matching quote or a meridiandispatch.com source. It does not add format or length guidance beyond what the schema already supplies.

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 verb and resource ('Tell the Meridian Dispatch desk that a fact on one of its pages still holds') and immediately scopes it with the required evidence ('with the current, independent source that shows it'). It also distinguishes itself from the sibling tool that handles the opposite case ('If the fact is wrong instead, use suggest_edit'), so an agent can route without opening either schema.

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 gives an explicit trigger ('Use it when the traveller confirms a fact on a page (they were just there, or asked you to check it and the source agrees)') and an explicit alternative for the inverse case ('use suggest_edit'). The preconditions for acceptance are also spelled out (quote must appear on the page, source must not be on meridiandispatch.com), leaving nothing to inference.

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