delete_resource_group

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

With no annotations, the description must disclose behavioral traits. It only states 'delete' but does not explain whether the operation is irreversible, what happens to associated resources, or what permissions are needed. This is insufficient for a mutable operation.

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 very concise at one sentence, but it omits necessary details. While not verbose, it under-specifies the tool's behavior, which reduces effectiveness.

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?

Given the tool's complexity (1 parameter, no annotations, output schema exists but unmentioned), the description is far from complete. It should explain the effect, permanence, and output format. Currently it lacks critical context.

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 single parameter 'group_id' is not explained in the description. Schema coverage is 0%, so the description adds no meaning beyond the schema's type definition. The agent must infer what constitutes a valid group_id.

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 resource (resource group), making the purpose immediately understandable. However, it does not distinguish this tool from siblings like 'update_resource_group' or 'create_resource_group', lacking context on uniqueness.

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, no conditions for deletion (e.g., resource must exist), and no mention of prerequisites. It fails to help the agent decide to invoke this tool.

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