wikijs_delete_page

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

Without annotations, the description partially discloses behavior: it explains the conditional nature of the confirm parameter and required permissions. However, it does not describe what happens upon deletion (e.g., irreversibility, cascading effects, or return value).

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?

Three concise sentences, each serving a distinct purpose: purpose, prerequisites, and parameter nuance. No wasted words, front-loaded with the core action.

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 a simple two-parameter deletion tool with no output schema, the description covers prerequisites and a parameter behavior, but lacks information about the result or side effects (e.g., success indicator, idempotency). Adequate but not complete.

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 coverage is 100%, but the description adds value by naming the env var WIKI_MUTATION_CONFIRM_TOKEN and clarifying the confirm parameter's requirement condition, which goes beyond the schema's description.

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 verb 'Delete a page by ID', identifying the resource and method. Among sibling tools, it distinguishes itself from delete_comment and delete_tag by specifying '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 prerequisites (WIKI_MUTATIONS_ENABLED and permissions) but does not offer guidance on when to use this tool versus alternatives like move_page or restore_page. No when-not-to-use or contextual comparison is given.

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