control_gap_analysis

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

No annotations are provided, so the description must carry the full burden. It mentions 'analysis' and 'roadmap' but does not disclose idempotency, side effects, authorization requirements, rate limits, or whether it mutates data. The term 'deep-dive' suggests computational cost but is not explicit.

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 a single sentence, very concise with no wasted words. However, it is too brief and could be expanded slightly without losing conciseness.

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 5 parameters (2 required), no output schema, and a complex domain (compliance), the description is insufficient. It does not specify supported frameworks, output format, or how it differs from sibling tools. A more complete description would add value.

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 description coverage is only 20% (1 of 5 parameters documented in schema). The description provides no parameter details. While the schema lists enums and requirements, the description adds no meaning beyond what schema offers. The previous_scan_id parameter has a detailed description in schema, but that is not part of the description field.

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: 'deep-dive analysis' and 'remediation roadmap'. The verb 'analysis' and specific domain 'compliance control gaps' make the purpose clear. However, it does not differentiate from similar sibling tools like compliance_framework_check or audit_report_generate.

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?

No guidance on when to use this tool versus alternatives. No prerequisites, exclusions, or context for invocation. The description is silent on usage boundaries.

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