Delete Group Wiki Page

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

The description adds 'irreversible' and 'permanently' beyond the annotation's destructiveHint=true, emphasizing the permanence. It aligns with annotations and provides useful context.

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 very concise with three punchy sentences: action, consequence, and requirements. No wasted words, and key info is front-loaded.

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 two parameters and no output schema, the description covers the core use case, irreversibility, and a recommended pre-check. It lacks specifics on permissions or error handling but is generally complete.

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?

With 0% schema description coverage, the description must compensate but only states 'Requires group_id and slug' without explaining what each parameter represents or their formats. This adds minimal 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 'Delete a group wiki page permanently' with a specific verb and resource. It distinguishes from sibling tools like gitlab_delete_wiki_page by specifying 'group' 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?

The description provides a recommended pre-check (gitlab_get_group_wiki_page or gitlab_list_group_wiki_pages), which guides proper use. However, it does not explicitly differentiate from alternatives like deleting project wiki pages.

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