provider_delete_group

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond the raw route: it does not say whether dependent memberships/roles are removed, whether deletion is reversible, or what errors occur for a nonexistent or protected group.

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 short lines, front-loaded with the action, with zero filler. It is efficient, though the second line largely duplicates the annotation title.

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, single-parameter delete with no output schema and full annotation coverage, the minimum is present. Missing is anything an agent would want before committing an irreversible operation: cascade behavior and permission requirements.

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?

One required path parameter with 100% schema coverage, so the baseline is 3. The description's endpoint template does confirm groupUrn is a path segment, but it gives no format or example (URN vs UUID) beyond what the schema says.

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 the specified group') and appends the exact HTTP endpoint, so an agent can tell it apart from provider_create_group / provider_update_group / provider_query_groups. It stops short of naming a sibling or scoping what a 'group' is in this provider context.

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?

There is no when-to-use guidance, no prerequisites (permissions, ownership), and no mention of alternatives such as provider_update_group or provider_delete_user. The endpoint path is the only contextual clue, which the agent must infer from.

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