yougile_delete_project_role

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

Annotations already mark this as destructive (destructiveHint=true), and the description adds the key behavioral trait that this is a hard delete, meaning permanent removal rather than a reversible soft-delete. This goes beyond the structured annotations by clarifying the irreversibility, which is valuable 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 a single, efficient sentence that fully conveys the purpose and key nuance (hard delete). There is no redundant information or filler.

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 operation with two well-documented UUID parameters and clear destructive annotations, the description adequately covers the core behavior. The explicit mention of hard-delete addresses the main side-effect concern, though it stops short of describing cascading effects or return values, which are less critical here.

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% with both parameters documented as 'Role UUID' and 'Project UUID'. The description adds no extra meaning beyond the schema, so it performs at the baseline for fully covered schemas.

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 states a specific action 'Delete a project role' with the resource clear. It distinguishes itself from potential soft-delete variants by explicitly noting '(hard delete, not soft-delete)', so there is no ambiguity about the operation.

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?

No guidance is given on when to use this tool versus alternatives. The description doesn't mention prerequisites, conditions, or suggest when a hard delete is appropriate, leaving the agent to infer usage only from the tool name and generic action.

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