generate_compliance_report

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

With no annotations, the description must carry the full burden of behavioral disclosure. It describes report contents but does not clarify side effects, return format, whether it persists data, or prerequisites (like results from a prior audit). This leaves the agent uncertain about the tool's operational impact.

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 that is front-loaded with the main verb and object, and it contains no filler. It efficiently lists formats and key contents, though it could be structured into two sentences for even better readability.

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's complexity (4 parameters, nested results object, no output schema), the description provides a reasonable summary but misses key contextual details: it does not mention the required 'results' parameter, describe the return value shape, or explain how it differs from other reporting tools. This is adequate but not complete.

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 100%, so the baseline is 3. The description adds limited semantic value, only mentioning the 'optional remediation plan' which maps to includeRemediation. It does not elaborate on level or format relationships beyond what the schema already provides.

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 with a specific verb ('Generate'), the resource ('compliance reports'), and enumerates supported formats (VPAT, WCAG, ADA, Section 508). It also lists key report contents, distinguishing it from sibling tools like generate_summary_report or export_to_html_report.

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 implies usage for generating compliance reports in specific formats, but it does not provide explicit exclusions or comparisons with alternative tools. Since siblings like generate_summary_report and export_to_html_report overlap, more guidance on when to prefer this tool would be useful.

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