wikijs_delete_page

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the core destructive action and omits critical context such as whether deletion is permanent, whether child pages or linked content are affected, or if any confirmation/permission is required. This is a significant gap for a mutation 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 a single, clear sentence with no wasted words. It is appropriately sized for a one-parameter tool and the core action is front-loaded, making it easy for an agent to parse quickly.

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?

Despite the tool's low parameter complexity, it is a destructive operation with no annotations and no output schema. The description is too spare: it does not mention whether the deletion is reversible, what happens on success or failure, or any side effects on related content. More behavioral context is needed for an agent to invoke it safely and correctly.

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 schema has 100% description coverage, so the baseline is 3. The description's 'by ID' merely echoes the schema's 'Page ID to delete' and adds no new meaning, such as the ID format, source, or behavior when the ID does not exist.

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 uses a specific verb ('Delete') with a clear resource ('a page') and method ('by ID'). This distinguishes it from sibling tools like wikijs_update_page, wikijs_get_page, and wikijs_create_page, since no other sibling deletes a 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 no guidance on when to use this tool versus alternatives such as wikijs_update_page, which might be used to deactivate or repurpose a page instead of deleting it. There are no stated conditions, prerequisites, or exclusions; usage is only implied by the verb 'Delete'.

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