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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds a genuinely useful constraint not in annotations: only empty, non-first pages can be deleted. It doesn't state whether deletion is permanent or how failures surface, but the added precondition is solid context.

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 tight sentences with zero waste. The core action is front-loaded, and the crucial constraint follows immediately.

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 mutation with no output schema, the description covers the key constraint on when deletion succeeds. Minor gaps remain — whether the deletion is permanent, and what happens to a page's content if it is non-empty — but the essential calling information is present.

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?

Only one parameter (page_id) exists and schema description coverage is 100%, so the schema already documents the input. The description adds no syntax or format guidance beyond the schema. Per the high-coverage rule, a baseline of 3 is appropriate.

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 states a specific verb (delete) and resource (page), and the second sentence scopes it further by requiring an empty, non-first page. The resource is unambiguous against the many delete_* siblings (delete_channel, delete_team, delete_monitor), so an agent can route correctly.

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 states the preconditions for use: the page must be empty and must not be the first page. However, it gives no alternative or next-step guidance (e.g., what to do if the page still has content, such as update_page to empty it first), so the exclusions are clear but the workaround path is left implicit.

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