delete_page

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

With no annotations provided, the description must disclose behavioral traits. It does reveal a key destructive side effect: deleting a page also deletes all its entries. However, it lacks any mention of irreversibility, permissions, or what happens to linked data, leaving significant behavioral 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?

The description is a single, front-loaded sentence that conveys the essential action and its primary consequence. Every word is meaningful, with no filler or unnecessary detail.

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 destructive tool with one parameter and no output schema, the description is adequate but incomplete. It lacks context such as permanence, required permissions, or what qualifies as a 'page'. Given the destructive nature, a stronger warning or precondition would improve completeness, but the cascade note mitigates some ambiguity.

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?

The schema has one parameter ('page') with 0% description coverage, so the description must compensate. It mentions 'a page' but does not clarify the expected format (e.g., ID, name, path) or relationship to the parameter. The parameter name alone is insufficient, and the description adds little semantic value beyond restating the resource.

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 'Delete a page and all its entries' uses a specific verb ('delete') and resource ('page') while explicitly noting the cascading effect on entries. This distinguishes it clearly from sibling tools like delete_entry, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives (e.g., delete_entry for entries only). It does not state prerequisites, alternatives, or situations where it should be avoided, offering only the basic action.

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