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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the agent knows this is a non-destructive but non-idempotent trigger. The description reinforces that it forces an immediate check, but says nothing about rate limits, latency, or that the schema's 'confirm' guard may be invoked for hard-to-undo actions.

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 front-loaded sentence that names the action, the timing rationale, and the return value with 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?

With no output schema, the description usefully states that the deliverability view is returned, and it explains the trigger semantics. It omits behavior around repeated triggering and any delay before results are ready, which would round it out.

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% and both parameters (app_id with default fallback, confirm for guard approval) are fully documented in the schema. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 verb and resource: re-running the From-domain DNS check on demand rather than waiting for the scheduled daily check. It also notes the deliverability view is returned, which slightly overlaps with the get_deliverability sibling but still lets an agent tell the trigger-oriented tool apart from the pure read tool.

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?

Gives clear use context: use it 'now (after a fix)' instead of waiting for the daily check. That is a concrete when-to-use signal. It does not explicitly name get_deliverability as the alternative for simply reading results, so the exclusion is only implied.

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