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

With no annotations provided, the description must carry the behavioral burden, and it does disclose that pending deliveries will stop. It still omits important mutation details such as whether deletion is irreversible, permission requirements, and whether existing delivery history remains accessible.

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 two short, front-loaded sentences with no wasted text. The primary action is stated first and the consequence second.

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 single-parameter deletion tool with no output schema, the description is minimally sufficient: it states the action and one consequence. It is incomplete for a destructive operation because it does not mention irreversibility, authorization, or what happens to past deliveries.

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%, and the description does not explain the required endpoint_id parameter. The parameter name is largely self-explanatory, but the description adds no detail on where to obtain it or its expected format.

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 gives a specific verb and resource: "Remove a webhook endpoint." It is clear what operation is performed, though it does not explicitly differentiate this from related sibling tools such as homeowner_webhookDelete.

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?

Usage is implied by "Remove a webhook endpoint," and the side effect on pending deliveries is noted. However, there is no explicit guidance on when to choose this over alternatives or prerequisites such as finding the endpoint_id via webhooks_list.

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