deleteGroup

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not indicate whether the deletion is irreversible, cascades to related resources, or requires special authorization, offering minimal transparency.

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 extremely concise at two words, but it is under-specified. It lacks necessary detail for effective tool use, and while front-loaded, it does not adequately serve the agent.

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 absence of an output schema and annotations, and a single nested parameter, the description is insufficient. It does not explain return behavior, side effects, or parameter usage, making it incomplete for a deletion action.

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%. The description adds no meaning to the input schema parameters; it does not explain that pathParams contains format and groupId, nor their roles. The schema provides inherent structure but the description adds no value.

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 'Delete group' clearly states the verb and resource, indicating the tool deletes a group. It distinguishes itself from sibling tools like createGroup or getGroup, though it lacks nuance about whether the deletion is permanent or soft.

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 provided on when to use this tool versus alternatives like updateGroup or archiveProject. There is no mention of prerequisites (e.g., group existence, permissions) or exclusions.

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