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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new fact beyond the structured fields - the required systems:write scope - but says nothing about duplicate-name behavior, validation failures, or what identifies the created group.

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, front-loaded with the core action and hierarchy, followed immediately by the permission requirement. No filler, no repetition of the title.

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 low-complexity create tool with a fully described 3-parameter schema, no output schema, and annotations covering the safety profile, the description supplies the essential missing pieces: what a system group is in the hierarchy and the required scope. The remaining gap is behavior on duplicate or invalid input, which is a minor omission here.

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%, so all three parameters (name, description, system_class_id) are already documented in the schema with constraints. The description adds conceptual context that a group sits under a system class, hinting at the role of system_class_id, but no format or constraint detail beyond the schema. Baseline 3 applies.

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 and resource ('Create a new system group') and further disambiguates with a hierarchy definition ('category under a system class') and concrete examples ('Heating', 'Cooling'). It does not explicitly contrast with the near-identical sibling create_project_system_group, which keeps it just shy of a 5.

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?

There is no when-to-use vs when-not-to-use guidance, no prerequisites such as the parent system class needing to exist, and no mention of alternative tools like bulk_create or create_system_class. The only conditional statement is the auth scope, which is a permission requirement rather than usage guidance.

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