Delete Achievement

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is covered. The description adds meaningful context beyond that: deletion cascades to all awarded and revoked instances and requires Maintainer/Owner permissions. It could further clarify irreversibility or response behavior, but the key behavioral risk is disclosed.

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?

Two compact sentences with no waste. The destructive scope is front-loaded, followed by the permission requirement, making the most important facts immediately visible.

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 destructive delete tool with full schema coverage and explicit annotations, the description covers the essential cascade and authorization details. It does not describe the return value, but with no output schema this is a minor gap rather than a blocking omission.

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 100%, and the schema already explains that achievementId accepts a numeric ID or GitLab GID and that userCredentials falls back to the environment token. The description adds no parameter-specific detail, so the baseline of 3 is appropriate.

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?

States a specific verb (delete) and resource (group achievement), and adds scope detail: every related awarded or revoked instance. This clearly distinguishes it from sibling tools such as create_achievement, update_achievement, award_achievement, and revoke_achievement.

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?

Provides clear operational context by declaring the action destructive and requiring group Maintainer/Owner permissions. It does not explicitly say when to use revoke_achievement instead of deleting the whole achievement, but the scope difference is strongly implied.

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