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

Annotations already declare this as a safe, idempotent, non-destructive read, so the safety profile is covered. The description adds value beyond that by disclosing the invocation constraint ('one is required') and the shape/meaning of returned link fields (required_frequency_days semantics, weight).

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?

Three compact sentences, front-loaded with the purpose and followed by the invocation constraint and return-field meaning. Every sentence carries weight, though it is slightly dense in the final sentence.

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?

With no output schema, the description usefully describes the returned link fields (required_frequency_days, weight). For a two-param junction-list tool with full schema coverage and read-only annotations, this is nearly complete; only the 'one is required' wording versus an empty required array in the schema leaves minor ambiguity.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that passing compliance_item_id lists PM schedules and the reverse lists compliance items, plus the mutual-exclusivity/one-required rule. This clarifies each parameter's effect rather than just restating it.

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 (PM schedules linked to a compliance item), and crucially explains the bidirectional nature of the junction ('or the compliance items a PM schedule counts toward'). This clearly distinguishes it from the singular get_compliance_pm_schedule and the general list_pm_schedules.

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 provides clear invocation context by explaining the two modes (filter by compliance item vs. by PM schedule) and the constraint that one ID is required. It stops short of naming alternatives or exclusions (e.g., vs. get_compliance_pm_schedule), so it is clear context but not fully explicit routing.

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