delete_page

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

Annotations already indicate destructive behavior. The description adds the return shape '{ ok, nodeId }' and the constraints about current/last page. No contradictions with annotations.

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 concise sentences, front-loaded with the primary action and constraints. Every sentence provides value with no redundancy.

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?

The description covers the action, constraints, and return value. For a simple delete operation with one required parameter and no output schema, this is largely complete. It could optionally mention error conditions (e.g., if pageId is invalid), but current content is adequate.

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 single parameter 'pageId' is fully described in the schema with 'Page id to delete'. The description adds no further semantic context beyond the schema, and schema coverage is 100%.

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 clearly states 'Delete a page by id', specifying the verb and resource. It also includes constraints ('cannot delete current page and last remaining page') which distinguish it from sibling tools like delete_nodes that delete other node types.

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 explicitly notes that the current page and last remaining page cannot be deleted, providing when-not-to-use guidance. However, it does not directly contrast with sibling tools like delete_nodes or navigate_to_page, leaving some grey area.

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