Delete Page (ADMIN)

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, covering the core behavioral safety profile. The description adds the ADMIN key requirement, which is meaningful auth context. However, it doesn't disclose what happens to associated content blocks, widgets, or related resources when a page is deleted, nor whether deletion is reversible.

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?

One sentence, zero waste, directly meaningful. The title 'Delete Page (ADMIN)' also reinforces purpose. Perfectly concise.

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?

This is a destructive mutation tool with no output schema, 0% parameter coverage, and no behavioral notes about consequences or irreversibility. The description is far too thin for the risk profile of the operation. It should mention what dryRun does, whether deletion cascades to content blocks/widgets, and error conditions. Given the destructive nature, this level of underspecification is a significant gap.

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 adds no parameter meaning beyond the schema. The schema reveals portalRef and pageRef (both minLength 1 strings, self-explanatory) and dryRun (boolean, default false), but the description doesn't explain what dryRun does, what format portalRef/pageRef take, or what the ADMIN key requirement means for invocation. With 0% coverage the description must compensate and does not.

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) and resource (page), which distinguishes it from sibling tools like kilango_create_page, kilango_update_page, and kilango_get_page. The 'Requires an ADMIN key' clause adds a privilege qualifier. However, it doesn't explicitly distinguish from kilango_delete_portal or other delete siblings at the same level of clarity, though the resource is clearly '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?

There is no guidance on when to use this tool vs alternatives. It doesn't mention that it may be safer to first use dryRun, or that get_page/list_pages might be helpful before deleting. The ADMIN key requirement is a gate but not contextual guidance about when deletion is appropriate or how it relates to publishing/archiving alternatives among siblings.

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