delete_group_wiki_page

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

No annotations are provided, so the description carries full burden. While 'delete' implies a destructive action, it lacks details about side effects (e.g., whether the page is permanently removed, if history is affected) or required permissions. More behavioral context would be expected given the lack of annotations.

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, concise sentence that efficiently conveys the core purpose. However, it could be slightly expanded with essential details (e.g., required parameters) without becoming verbose.

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 simple delete tool with no output schema, the description adequately identifies the resource and action. However, it fails to specify that both parameters are likely required (despite the schema lacking 'required'), and it does not describe the expected response, leaving the agent with some uncertainty.

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?

The input schema has 0% description coverage, and the description does not explain the meaning of 'group_id' or 'slug'. The agent gets no additional semantic information beyond the parameter names, which is insufficient for correct invocation.

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 target resource ('a wiki page from a GitLab group'), which distinguishes it from sibling tools like 'delete_project_wiki_page' and 'edit_group_wiki_page'. However, it doesn't explicitly state that the deletion is permanent or irreversible.

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 (e.g., 'delete_project_wiki_page' for project-level pages) or any prerequisites (e.g., required permissions). The agent has no context to decide if this tool is appropriate.

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