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 a useful auth detail (project_system_groups:write scope) but does not disclose what removal entails, e.g., cascade effects on related systems or whether confirmation is required.

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, with the core verb+resource front-loaded and the prerequisite trailing. No wasted words, though the second sentence is a bare scope note rather than something more informative.

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 rich annotations and no output schema, the essentials are present, but the description omits anything about dependent data or post-deletion state, which is the main gap an agent would care about before calling a delete.

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% with a single clearly documented 'id' (uuid) parameter, so the schema carries the semantics. The description only restates 'by ID' without adding format or constraint detail beyond the schema, matching the baseline 3.

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 ('Remove') and resource ('a system group from a project') plus the identifier used, so the operation is unambiguous. It does not, however, distinguish itself from nearby siblings such as delete_project_system or delete_system_group, leaving the agent to infer which resource is which.

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 says nothing about when to use this tool versus the sibling delete_project_system, delete_system_group, or the list/get variants for confirming existence. The only guidance is the required scope, which is an authorization prerequisite rather than usage context.

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