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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the semantic framing of what a system group is, with no mention of pagination behavior or result size, which the schema handles instead.

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 clauses, zero filler, and the resource definition is front-loaded before the optional filter note. Every element earns its place.

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 zero-required-parameter read-only list tool with full annotation and schema coverage and no output schema, this is nearly enough. The remaining gap is disambiguation from the project-scoped sibling list_project_system_groups, which an agent may easily confuse with this one.

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 four parameters (page, search, per_page, system_class_id) are documented in the schema itself, including the auto-fetch pagination behavior. The description adds nothing beyond echoing the system_class filter, which matches the baseline of 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 and resource ('List system groups') and adds a clarifying gloss with examples ('categories of systems, e.g., "Heating", "Cooling"'), so the agent knows what a system group is. It does not, however, distinguish this global list from the sibling list_project_system_groups.

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 only guidance is 'Optionally filter by system class,' which is parameter behavior rather than when-to-use advice. Nothing tells the agent when to pick this over list_project_system_groups or list_systems, or whether it needs a project context.

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