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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds useful domain semantics about what each link carries (required_frequency_days, weight), but says nothing about pagination or result volume. With annotations carrying the behavioral load, this is a modest add.

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 tight sentences: the bidirectional purpose first, the call constraint second, the payload meaning third. No filler sentences and nothing repeated from 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?

With no output schema, the description helpfully explains the two fields each link carries, which is what an agent needs to interpret results. It stops short of noting pagination/limits or that the response may be empty for a valid ID, minor gaps for a listing endpoint.

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% and each parameter already points at its resolver tool (list_pm_schedules, list_compliance_items). The description adds the critical non-schema constraint that one of the two is required (schema declares zero required params) and explains the linked semantics of the returned fields, which compensates for the schema's silence on the mutual requirement.

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+resource (list PM schedules linked to a compliance item) and goes further by naming the reverse direction (the compliance items a PM schedule counts toward), which distinguishes it from list_pm_schedules, list_compliance_items, and get_compliance_pm_schedule. An agent can tell what this join-listing tool does without opening the schema.

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?

Explicitly states that exactly one of compliance_item_id or pm_schedule_id must be passed, which is the key usage decision. It does not, however, name the sibling tools an agent should use instead when it wants the underlying PM schedules or compliance items themselves, so alternative-routing guidance is only partial.

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