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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds essentially no behavioral context of its own — nothing about the automatic multi-page fetching, result volume, or default cursor behavior, which is the one genuinely non-obvious trait of this tool (though the schema does mention it).

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 resource definition front-loaded and the filter hint second. Nothing to trim and nothing 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 read-only, no-required-param list tool with full schema coverage and rich annotations, the description covers the essentials. It could optionally note that unpaginated calls fetch all pages, but the schema already carries that detail, so the gap is minor.

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 five parameters are already documented with types, ranges, maxLength and defaults. The description's 'filter by status or system' merely names two of them and adds no syntax, format, or default detail. Baseline 3 per the schema-coverage rule.

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 (compliance items), with a parenthetical that defines what a compliance item is: 'regulatory requirements tracked against PM schedules.' That disambiguates it from nearby siblings like list_compliance_records and list_compliance_pm_schedules, though it never names an alternative explicitly.

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?

'Filter by status or system' implies how the tool is scoped in practice, but there is no statement of when to use this versus list_compliance_records or get_compliance_item, and no prerequisites or exclusions. 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.