Crosswalk between frameworks

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds a genuinely non-obvious caveat: the mapping is the project's own analysis, not an official NCA mapping. It does not elaborate on return structure or size, but against these annotations that is a minor gap.

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?

Four tight sentences, front-loaded with the general rule ('map in either direction at the subdomain level') before the per-framework branches. Every sentence carries unique information; the only mild redundancy is restating the return targets per branch.

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?

There is no output schema, so the description must convey what comes back, and it does name the returned content per direction (ISO/NIST references or ECC subdomains). It stops short of describing the shape of those results, which an agent doing programmatic json processing might still need to discover.

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 only 50% (id and framework have no schema descriptions), so the description carries real burden and does so: it defines the accepted framework values and the id format expected for each ('2-8', 'A.8.24', 'PR.DS'). The lang and response_format enum descriptions are left to the schema, which is fine.

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 (map) and resource (frameworks) with the precise granularity: 'subdomain level'. The description makes clear it is bidirectional and returns ISO 27001 / NIST CSF 2.0 cross-references, which distinguishes it from siblings like ecc_get_control or ecc_list_subdomains.

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?

Gives explicit when-to-use detail per input: 'ecc' + subdomain code to go outward, 'iso27001' + reference, 'csf2' + category to go inward. Each branch is illustrated with a concrete example value ('2-8', 'A.8.24', 'PR.DS'), leaving nothing to inference.

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