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

Annotations already declare destructiveHint=true, so the safety profile is covered structurally. The description adds real value beyond that: it stresses PERMANENT deletion, states that live status-page data is modified, and explicitly says the action cannot be undone — concretely describing what is destroyed. It stops short of auth requirements or error behavior.

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 sentence with the destructive warning front-loaded, followed by the endpoint mapping. Efficient, though the caps emphasis and the REST path add little for an agent that already has the schema.

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 2-required-param destructive tool with no output schema and full schema coverage, the description covers the critical concerns: permanence, irreversibility, and that live data is affected. Only error/edge-case behavior (e.g., deleting an active maintenance) is unaddressed.

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 100%, so both page_id and maintenance_id are already documented in the schema. The description only adds 'by id', which does not extend beyond the schema's own descriptions; baseline 3 applies.

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 (PERMANENTLY DELETES) and resource (scheduled maintenance) scoped by id, and names the exact REST endpoint. An agent can distinguish it from instatus_delete_incident and instatus_update_maintenance without opening a schema.

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?

The description says what it deletes but never states when to use it versus alternatives (e.g., cancel vs. delete, or delete_incident) nor any prerequisites such as required permissions or that the maintenance must not be in progress. Usage is only implied by the tool name and endpoint.

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