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

Annotations already supply destructiveHint=true and readOnlyHint=false. The description adds no behavioral context beyond the raw delete action, such as cascading removal of widgets, permanence, or authorization requirements.

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?

One short, front-loaded sentence with no filler. It delivers the core action and object immediately and earns every word.

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 one-required-parameter destructive operation with safety annotations and an output schema, the minimal description is sufficient for invocation. It could add a note about whether the page's widgets are deleted too, but that is not essential for the agent to call the tool correctly.

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 100% and the page_id property is already described ('Page ID to delete (from list_pages)'). The description merely echoes 'by ID' and contributes no new parameter semantics, so the high-coverage baseline of 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 ('Delete') and resource ('a page by ID'), and the title narrows it to report pages. This is clearly distinct from sibling tools like delete_widget, delete_folder, and delete_connection.

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 intended use is implied by the verb—call it when a page needs to be removed—but there is no explicit when/when-not guidance or comparison to alternatives. With many archive_* and delete_* siblings, a sentence saying 'permanently removes a page; use archive_* to keep it recoverable' would materially improve routing.

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