purge_page

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

The description discloses the irreversible nature (content cannot be recovered) and the prerequisite (page must be trashed). With no annotations provided, this carries full burden and is sufficient for a simple deletion tool.

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 very concise: two sentences, the first stating the purpose and the second emphasizing irreversibility and prerequisite. No unnecessary words 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?

For a simple deletion tool with no output schema, the description covers the core behavioral aspects (irreversible, prerequisite). It lacks details on return values or error handling but is otherwise complete for typical usage.

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 input schema has 0% description coverage for the two required integer parameters (collectiveId, pageId). The description does not explain their meanings or provide additional context beyond their names, failing to compensate for the lack of schema descriptions.

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 the tool permanently deletes a trashed page, specifying the action (permanently delete) and the resource (trashed page). It distinguishes from siblings like delete_page (which likely moves to trash) and restore_page.

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 explicit prerequisite: the page must be in the trash (use delete_page first). This guides the agent on when to use this tool vs alternatives. However, it does not explicitly state when not to use it (e.g., if page is not trashed).

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