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

Discloses that it sends a webhook (side effect), explicitly states 'No incident or score change,' and adds rate limit and permission requirements. This goes beyond the annotations (readOnlyHint=false, destructiveHint=false) by clarifying the exact nature of the side effect and constraints.

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?

Three concise sentences, front-loaded with purpose, then constraints, then post-action guidance. No wasted words; every sentence earns its place.

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?

Complete for a simple test tool: purpose, constraints, and clear post-action guidance. Since an output schema exists, return values are covered by that. Nothing an agent needs to call it correctly is missing.

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 has no descriptions for agent_id and api_key, and the description doesn't explain them. It implies agent_id identifies the webhook and api_key is for authentication, but this is not explicit. With 0% schema coverage, the description should compensate, but it doesn't.

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 exactly what it does: 'Send one signed incident.test to your configured webhook.' This is a specific verb and resource, and the additional constraints (owner-only, once/minute) help distinguish it from other agent tools like health checks or endpoint assessments.

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 clear usage constraints: 'Owner-only, once/minute' and instructs to 'Inspect delivered and receiver_status; do not automatically replay.' While it doesn't explicitly name alternatives, the context is clear enough for an agent to know when to call it and what to do afterward.

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