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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral detail beyond that: the response embeds linked PM schedules and their required frequencies, which is not derivable from the annotations or input schema.

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?

A single sentence that leads with the action and resource, then appends the most decision-relevant return detail. Zero filler or redundancy.

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 carries some burden for describing returns and does so partially by naming the linked PM schedules and frequencies. Remaining fields of the compliance item are undocumented, but for a simple single-ID fetch with a fully documented parameter, this is nearly complete.

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?

There is one parameter (id, UUID) at 100% schema description coverage, so the schema already documents it completely. The description adds no syntax, format, or lookup semantics beyond the parameter name, which is the expected baseline when the schema does the heavy lifting.

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 (Get) and resource (compliance item) and specifies the payload's notable contents: linked PM schedules and their required frequencies. It does not explicitly distinguish itself from siblings like list_compliance_items or get_compliance_pm_schedule, but the singular 'item' and detail-oriented phrasing make the intent clear.

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?

No guidance on when to use this tool versus list_compliance_items (for enumerating) or get_compliance_pm_schedule (for fetching a single schedule). The agent must infer that this is the single-record fetch by ID.

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