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

The annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered. The description still adds real value by disclosing cascade behavior ("and its components"), which the annotations do not convey, plus an invocation guardrail.

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?

Two short sentences with zero filler; the destructive scope is front-loaded and the constraint follows immediately. Nothing could be removed without losing information.

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?

Cascade destruction and the user-intent guardrail are covered, and no output schema is needed for a delete. But with zero schema documentation for the required slug and no pointers to list_status_pages as the source of a valid slug, an agent can still call this with an unusable identifier.

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 coverage is 0% for the single parameter, so the description carries the full burden for "slug" and gives nothing — no format, no indication of how a slug differs from a page ID, no example. An agent must guess whether the slug is the page identifier returned by get_status_page/list_status_pages.

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+resource ("Delete a status page") and adds the important scope detail that its components go with it. It is clearly distinguishable from delete_component and delete_check by resource, though it never names a sibling explicitly.

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?

"Run only when the user asked to delete this page in this conversation" is an explicit precondition that prevents an agent from proactively cleaning up pages. It gives a clear when-to-use rule but no alternatives or prerequisites (e.g. what happens if the page is linked elsewhere).

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