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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the idempotency intent (avoid duplicate sends), which is genuinely useful context, but says nothing about the fact that this is a live, outbound check against the destination (latency, possible rate limits, or that the destination may be unreachable), nor what it reports 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?

A single short sentence with the intent front-loaded and no wasted wording. It is efficient, though its brevity is part of why other dimensions are under-served rather than a stylistic flaw in itself.

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?

There is no output schema, so the description carries the burden of explaining what a 'check' returns (a boolean, a delivery record, a mismatch report?), and it does not. Combined with two undocumented required IDs and no note on what an uncertain send means operationally, the definition is too thin for the agent to call this confidently.

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 0%: both required parameters (connection_id, export_id) are bare strings with no documentation. The description does not compensate at all — it never mentions where the export_id comes from (presumably a prior send_to_destination or list_destination_exports result) or what connection_id refers to.

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 says it 'checks what arrived in a destination', which conveys a read/verification operation over a prior export, and the title adds 'uncertain send'. However, it never names the resource precisely (a destination export/delivery) nor distinguishes itself from close siblings such as get_delivery or list_destination_exports, so an agent must infer its niche.

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?

'so nothing is sent twice' implies the triggering condition: call this when unsure whether a previous send landed, before retrying. That is a useful implied context, but no alternative is named (e.g., list_destination_exports for browsing, send_to_destination for the actual send) and there is no explicit when-not guidance.

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