delete_project_role

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful behavioral context about edition/license/permission dependence and Community-edition 404 or empty-list behavior, which is beyond the 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?

Three short sentences, front-loaded with the action and endpoint. The availability caveat is useful, though the description is terse and could better organize the parameter or error details.

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, open-world delete operation with no output schema, the description covers availability and some error behavior. It still omits important context such as what exactly is removed, cascading effects, and permission requirements beyond a general mention.

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 0%, so the description must compensate for parameter meaning. It only restates project_id and role_slug as path parameters in the DELETE route, without explaining formats, constraints, or how role_slug should be obtained.

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 and resource: 'delete project role.' It is clearly a deletion operation, though it does not explicitly distinguish itself from sibling tools like update_project_role or delete_global_role beyond the name/resource.

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 contextual caveats about availability depending on edition, license, and permissions, and notes possible 404 or empty-list responses. However, it does not explicitly say when to use this tool versus alternatives such as update_project_role or delete_global_role.

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