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

With no annotations, the description carries the full behavioral burden and does so richly: it discloses cascading deletions, two safety layers (exact name confirmation and per-user 5/day destructive cap), and the anti-injection rationale behind the confirmation field.

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 front-loaded with purpose and cascade effects, then uses a compact numbered list for safety constraints. Every sentence adds meaningful operational guidance, including why the confirmation requirement exists and where to go for bulk operations.

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 dangerous mutation tool with no annotations, no output schema, and a minimal two-parameter schema, the description supplies the destructive behavior, cascade consequences, confirmation mechanics, rate limit, and alternative paths. Nothing essential 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?

Although schema description coverage is 0%, the description thoroughly documents the non-obvious confirmation parameter—exact match, case-sensitive, whitespace-trimmed, and how to obtain the name via describe_endpoint(id). The endpoint_id parameter is only implied, but its meaning is standard and sufficiently clear from context.

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 names a specific verb and resource: 'Delete a monitored endpoint.' It also states the cascade scope (test_results, baselines, regressions, incidents), making the operation distinct from sibling tools like pause_endpoint or describe_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?

It clearly explains when this tool is appropriate for single-endpoint deletion, and it explicitly routes legitimate bulk deletes to the HTTP API or dashboard. It does not directly compare against pause_endpoint, but the destructive nature is unambiguous.

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