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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context beyond restating the optional group filter already documented in the schema, such as pagination/auto-fetch behavior or return shape.

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 resource and examples front-loaded and no filler. It is efficient, though the second sentence carries little information beyond the schema.

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 simple read-only list tool with complete schema coverage and annotations carrying the safety profile, the description is nearly sufficient. Minor gaps (no mention of pagination defaults or against which siblings to choose) remain but are largely covered by structured fields.

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_group_id) are already documented in the schema. The description's only parameter reference, the group filter, duplicates what the schema states; 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 (List) and resource (systems), and the parenthetical examples (HVAC units, plumbing, electrical) disambiguate 'system' from siblings like list_system_groups, list_system_classes, and list_project_systems. It is clear, though it does not explicitly distinguish itself from those related list tools.

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?

'Optionally filter by system group' implies the primary use case, but there is no statement of when to prefer this over list_system_groups/list_project_systems or any precondition. Usage is implied rather than guided.

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