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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so safety is partly covered. The description's framing as a mere 'disable' softens what the annotations call a destructive operation, and it says nothing about reversibility, what happens to in-flight deliveries, or required permissions. This tension is a real risk for an agent deciding whether the call is safe.

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, front-loaded with the verb and resource, with no filler. Nothing is wasted.

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 destructive, non-idempotent mutation with two undocumented required parameters and no output schema, the description is too thin. It omits parameter meaning, reversibility, and the delete-vs-disable distinction that an agent needs to call it correctly.

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?

Both parameters (appId, endpointId) have 0% schema description coverage and the description adds no meaning for either. With low coverage the description is expected to compensate, and it does not mention parameters at all.

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 (disable) plus the resource (customer webhook endpoint) and the effect (no longer receives events), which is more than the title alone gives. However, the verb contradicts the tool name 'delete_endpoint', leaving an agent unsure whether the endpoint is removed or merely deactivated. It also does not distinguish the action from siblings such as update_endpoint.

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?

There is no guidance on when to use this versus update_endpoint, archive_source, or revoke_api_key, and no prerequisites or conditions given. The only usage signal is the implied effect of stopping event delivery.

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