deleteGroup

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

Annotations only provide readOnlyHint: false, implying a mutation. The description 'Delete group' confirms deletion but offers no additional behavioral context such as whether deletion is permanent, cascades to related entities, requires specific permissions, or has any irreversible consequences. With annotations being minimal, the description carries the full burden and fails to disclose anything beyond the obvious mutation.

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 short (two words), but this is under-specification rather than concise efficiency. It lacks any structure or front-loading of critical information. While there is no verbosity, the brevity results in significant information loss, so it does not meet the standard of good conciseness.

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?

With a nested object parameter, no output schema, and no parameter descriptions, the description is completely inadequate. An agent would need to guess the meaning of format and groupId, and how to structure the pathParams object. The description adds zero helpful context beyond the tool's name.

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 input schema has one required parameter (pathParams) containing format (enum json/xml) and groupId (number), but schema description coverage is 0% (no descriptions in JSON Schema). The description mentions nothing about these parameters, their purpose, or their constraints. The agent cannot infer how to fill pathParams from the description alone, making this a severe gap.

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' states a verb and resource, but it is essentially a restatement of the tool name 'deleteGroup' and adds no specific detail. It lacks any distinction from sibling delete tools (e.g., deleteIssue, deleteProject) other than the resource name, which is already in the name. This is borderline tautology, only slightly better than a pure restatement.

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 information about when to use this tool versus alternatives. It does not mention any prerequisites, side effects, or context that would help an agent decide when to call deleteGroup instead of other delete operations. There is zero guidance on usage conditions.

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