delete_page

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

With no annotations, the description reveals key behaviors: trashing (not permanent deletion), recoverability from trash, cascading subtree for folders, and a restriction on the Landing page. It lacks permissions or rate limits but covers essential traits.

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 every clause adds value. No fluff or repetition.

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?

Given low complexity and no output schema, the description covers purpose, recovery, subtree, and a restriction. It does not mention permissions or return values, but these are not required per rules.

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 documentation coverage is 0%, and the description adds minimal parameter meaning beyond names. It implies pageId is the page to delete and collectiveId identifies the collective, but no explicit details or examples.

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 it 'Trash a page' (specific verb and resource) and distinguishes from sibling tools like 'purge_page' and 'delete_collective', noting that folder pages cascade and the Landing page cannot be deleted.

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 provides clear context: use when you want to trash a page (recoverable from trunk), folder behavior, and that the landing page requires collective deletion. However, it does not explicitly contrast with 'purge_page' or other deletion tools.

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