map_compliance

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

Adds context beyond idempotent, read-only annotations: describes output (pass/fail/partial status), mentions caching behavior via force_refresh parameter, and output verbosity formats.

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?

Two sentences, no fluff, purpose and key details front-loaded. Every sentence adds value.

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?

No output schema, but description adequately covers output (status per control). With rich annotations and clear purpose, it is nearly complete for agent decision-making.

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 covers all parameters with descriptions (100% coverage). The description does not add new parameter details, so baseline score applies.

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?

Clearly states it maps scan findings to compliance frameworks (NIST, PCI DSS, SOC 2, CIS) and shows pass/fail/partial status. Distinguishes from sibling tools like check_spf or scan_domain.

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?

Implies usage for compliance assessment but does not explicitly state when to use this tool versus alternatives like individual check tools or batch scans.

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