conf_delete_page

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

The annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The phrase "move to trash" does add real value by implying a recoverable soft delete rather than a permanent purge, but the description says nothing about permissions required, whether child pages are affected, or how the page can be restored.

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?

A single five-word sentence with no filler and the action front-loaded. It is efficient, though the brevity shades into under-specification rather than tight, informative concision.

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 destructive, non-idempotent mutation with no output schema and 0% schema coverage, the description leaves out too much: permissions, effect on child pages, and recoverability/restore path. The annotations carry the risk signal, but the description does not fill the remaining gaps an agent needs before invoking a delete.

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 0% and the description does not explain pageId at all, so the description fails to compensate for the coverage gap. The single parameter name is largely self-evident, which keeps this from being a 1, but no format or sourcing guidance is added.

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?

"Move a page to trash" states a specific verb (move to trash) and resource (page), which reads as a soft delete and is distinguishable from conf_update_page or conf_get_page. It stops short of naming any sibling or clarifying the boundary with conf_update_page, so it is clear but not fully differentiated.

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?

There is no guidance on when to use this versus conf_update_page, and no mention of prerequisites such as ownership or admin rights. It also doesn't say whether this is the only deletion path or whether a permanent-delete variant exists.

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