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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds the 'Requires systems:write scope' authorization prerequisite, which is genuine value beyond the annotations, but it omits what deletion actually destroys (e.g., whether contained systems are orphaned or cascade-deleted).

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 sentences, zero filler, with the action and its key prerequisite front-loaded. Nothing is wasted or buried.

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 single-parameter destructive delete with annotations covering safety and no output schema, the description is minimally adequate. It lacks any note about side effects of the deletion or irreversibility nuance, which is the most relevant missing context for this class of tool.

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 100% and the single 'id' parameter is documented in the schema, so baseline 3 applies. The description's 'by ID' merely restates the schema and adds no format, range, or lookup detail beyond it.

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 gives a specific verb+resource ('Delete a system group') plus the identifier ('by ID'), clearly distinguishing it from sibling mutations like update_system_group or delete_system_class. It stops short of naming the resource grouping alternatives (delete_system, delete_project_system_group), so it is clear but not fully sibling-differentiated.

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?

Usage is only implied by the operation itself — an agent infers 'use this when you need to remove a group.' There is no explicit when-to-use/when-not guidance and no mention of alternatives such as update_system_group for non-destructive edits, so guidance is minimal.

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