Delete page

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

Annotations only declare openWorldHint=false, so the description carries the behavioral burden. It usefully discloses the guard rail ('refuses to delete the last remaining page'), which the annotations do not cover, but says nothing about irreversibility, confirmation, or what happens to page contents — significant gaps for a destructive operation.

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?

Three short sentences, front-loaded with the action, then the requirement, then the constraint. No wasted text.

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 simple no-output-schema delete tool, the description covers targeting and the key refusal condition. It leaves out what the call returns and whether deletion is reversible, which for a destructive tool leaves a small gap.

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 precedence rules are already documented in the schema (baseline 3). The description adds one thing the schema lacks — that at least one identifier is required (required parameters = 0 in the schema) — which is a genuine value-add.

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 and resource ('Delete a page (tab) from the current diagram') and clarifies the resource is a tab, which distinguishes it from siblings like rename_page, add_page and list_pages.

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?

Gives clear operating conditions: at least one of page_id/page_name/page_index is required, and deletion is refused when only one page remains. It does not explicitly route the agent among alternatives (rename_page, add_page), but the preconditions are stated precisely.

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