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

Annotations already declare read-only and idempotent behavior, so the bar is lower. The description adds valuable behavioral context by noting that these are 'practitioner mappings, not the NIST-published authoritative crosswalk,' which sets expectations about the reliability and origin of the mappings. No contradiction with annotations.

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 three concise sentences: the first states the core purpose and frameworks, the second lists valid input formats, and the third gives usage context. There is no fluff or redundant information; every sentence contributes meaningfully.

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?

The description covers purpose, input formats, and usage context well. However, since there is no output schema, it does not specify what the tool returns (e.g., the mapped control IDs or full crosswalk details). This is a minor gap, but the tool is simple enough that the return behavior can be inferred from the purpose.

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 covers the parameter fully, including examples and supported framework ids. The description repeats similar examples but does not add significant new meaning beyond what the schema already provides. With schema coverage at 100%, the baseline score of 3 is appropriate.

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 uses the specific verb 'map' and identifies the resource ('security control') along with the exact frameworks involved (800-171, 800-53, CSF, SOC 2). This clearly distinguishes the tool from sibling tools like lookup_control or list_controls, as it focuses specifically on cross-framework mapping.

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 explicitly states when to call the tool ('when the user asks what a control corresponds to in another framework') and gives an additional concrete use case (mapping existing FedRAMP/SOC 2/CSF work onto CMMC). It does not explicitly mention when not to use it or name alternative tools, but the usage context is clear enough to guide an agent.

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