deleteWikiPage

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 merely repeats the delete action implied by the tool name, without stating whether deletion is permanent, what cascading effects occur, whether special permissions are required, or what response to expect.

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 only three words, which is under-specification rather than genuine conciseness. It does not provide a sentence that earns its place; it restates the tool name without adding useful context or structure.

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?

The tool has a nested parameter object, no annotations, no output schema, and sits among 80+ sibling tools. The one-line description is completely inadequate to help an agent understand the deletion's effects, required inputs, or expected outcome.

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 explanation of pathParams, projectId, wikiPageTitle, or format. The schema itself defines these properties, but the description contributes zero additional meaning, so it fails to compensate for the complete lack of parameter documentation.

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 'Delete wiki page' clearly states the action (delete) and the resource (wiki page), distinguishing it from other delete tools like deleteProject or deleteUser. However, it does not elaborate on scope or behavior, so it is clear but lacks the sibling differentiation seen in higher-scoring examples.

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, no prerequisites, and no mention of when deletion should or should not be performed. There is also no reference to related wiki page tools such as updateWikiPage or getWikiPage.

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