deleteWikiPage

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

Annotations only declare readOnlyHint: false, indicating a mutating operation, which the description aligns with. However, the description adds no behavioral context—it does not mention whether deletion is permanent, cascades to attachments/versions, requires specific permissions, or can be undone. Given the sparse annotation coverage, the description should carry this burden but fails to.

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 short sentence, 'Delete wiki page', which is concise and front-loaded. However, it is so minimal that it borders on under-specification, offering no additional context or structure. It is efficient but not sufficiently informative relative to the complexity of the tool.

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 this is a mutating operation with a nested object parameter and no output schema, the description is entirely inadequate. It does not explain what happens on success or failure, the effects of deletion, or any constraints. An agent receives no guidance on return values, side effects, or conditions, making the tool very difficult to use correctly without external knowledge.

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%, so the description must compensate for the parameters (format, projectId, wikiPageTitle). It does not mention any of them, leaving the agent to infer semantics from names alone. The nested pathParams object and format enum are undocumented in the description, providing no added value beyond the schema.

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 action (delete) and the resource (wiki page), using a specific verb and resource combination. This distinguishes it from sibling tools like getWikiPage, updateWikiPage, and getWikiPageByVersion, making the purpose unambiguous.

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 prerequisites, conditions, or exclusions. While the action itself implies a clear scenario, there is no explicit context or mention of alternative tools or edge cases where deletion might be inappropriate.

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