cms_check_compliance

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

No annotations were provided, so the description must fully carry behavioral transparency. It clearly discloses the multi-tier resolution strategy and explicitly states that it reports coverage gaps. This gives the agent good understanding of what to expect.

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?

The description is two sentences long and front-loads the key information about the three tiers. The first sentence is dense but clear. Every phrase earns its place. Could be slightly more concise by removing the parenthetical list details.

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?

Given the single parameter, no output schema, and no annotations, the description provides a complete picture of what this tool does and its output (coverage gaps). It explains the multi-tier approach sufficiently for an agent to decide when to invoke it.

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?

The schema description coverage is 100%, so baseline is 3. The description adds value by explaining the topic parameter as 'Activity/process/method to check' and provides an example, but does not add additional semantics about format or constraints beyond the schema.

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?

The description clearly states the tool's purpose as a '3-tier compliance resolver' with explicit coverage reporting. It distinguishes from sibling tools like cms_gap_report and cms_coverage_scan by specifying the specific three tiers of sources checked.

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 gives context on when to use (to check compliance against multiple sources) and which tier is mandatory (Tier 2). However, it does not clarify when one might prefer this over the specific single-source tools like cms_bdlaws_act or cms_risk_lookup, nor does it explain when not to use it.

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