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

No annotations are provided, so the description carries the full burden. It states the tool returns mapping data, but does not disclose whether it is a read-only operation, any side effects, authentication requirements, rate limits, or error behavior. The brief 'Responses' section only lists a status code. Behavioral transparency is minimal but not contradictory.

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 core description is three concise sentences that cover purpose, functionality, and parameter usage. The appended 'Responses' section adds little value and could be omitted, but it does not detract significantly overall. The information is front-loaded and each sentence earns its place.

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 tool has no output schema and no annotations, the description explains what the tool returns (control-to-control mapping) and how to use it (exact framework names). This is largely sufficient for a simple mapping query. However, it does not describe the response format (e.g., whether it is a list, JSON structure, pagination), which could leave an agent guessing about how to parse results.

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 100%, with descriptive parameter names and examples. The description adds value by instructing to use exact framework names from agent_search_frameworks, which provides practical semantic guidance beyond the schema's type and examples. This helps the agent select correct parameter values.

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 verb 'Map controls' and the resource 'between two compliance frameworks'. It explains it returns a control-to-control mapping and enables multi-framework compliance. This distinguishes it from sibling tools like agent_get_framework_controls (single framework controls) and agent_coverage_report (coverage, not 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 provides explicit guidance to 'Use exact framework names as returned by agent_search_frameworks', which helps with parameter input. It also implies the use case ('enables multi-framework compliance') but does not explicitly compare to alternatives or state when not to use this tool. The context is clear, but exclusions are missing.

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