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

Beyond the annotations (destructiveHint=true), the description discloses specific side effects: the server purges the public URL, the resource is removed entirely, and it will no longer appear in listings. This is more detailed than the annotation alone.

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 sentences, tightly packed with essential information: the action, the side effect, the contrast with unpublish, and the irreversibility. No unnecessary 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?

The description covers the key caveats (purges URL, removes from listing, irreversible) and differentiates from the similar unpublish operation. Since there is no output schema, no return-value details are needed. The context for using this tool is fully addressed.

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?

The schema already describes endpoint_id as 'the endpoint id to delete,' which is clear and sufficient for a simple identifier. The description doesn't add extra detail, but given the high schema coverage, the parameter is well understood.

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 clearly states the action: 'Permanently delete a dynamic endpoint' with a specific verb and resource. It also distinguishes itself from the sibling 'unpublish' by explaining the difference, making its purpose unambiguous.

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?

It explicitly contrasts with unpublish: 'Unlike unpublish, this removes the resource entirely — it no longer appears in list_dynamic_endpoints.' This guidance helps the agent choose between delete and unpublish. It also warns 'Cannot be undone,' which is critical for a destructive operation.

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