Delete Wiki Page

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

Annotations already mark destructiveHint: true; description reinforces with 'Irreversible' and 'Requires slug'. Adds useful behavioral context beyond structured annotations without contradiction.

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 sentences, front-loaded with action and irreversibility. Every sentence provides essential information with no waste.

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?

For a destructive tool with no output schema, description covers irreversibility and pre-check recommendation. Lacks details on error handling or project_id usage, but adequate given the simple operation.

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 0%, but description explicitly states 'Requires slug', indicating the key parameter. Does not explain project_id, and the pattern/minLength details remain in schema only. Minimal value added beyond 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?

Clearly states the verb (delete), resource (wiki page), and key attributes (permanent, irreversible). Effectively distinguishes from sibling tools like gitlab_create_wiki_page or gitlab_update_wiki_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?

Recommends pre-checking with gitlab_get_wiki_page or gitlab_list_wiki_pages before deletion, providing clear context for use. Does not explicitly mention when not to use, but the guidance is helpful for correct invocation.

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