generate_audit_reports

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds minimal behavioral context by implying report generation with evidence, but doesn't detail output handling, file creation, permissions, or rate limits. With annotations providing core safety info, the description adds some value but lacks rich behavioral disclosure.

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, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a tool with many parameters, though it could be more front-loaded with key differentiators. Every word 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's complexity (8 parameters, nested objects) and lack of output schema, the description is adequate but incomplete. It covers the basic purpose but doesn't explain return values, error handling, or output file behavior. With annotations providing safety info and schema covering parameters, it meets minimum viability but leaves gaps for a generative tool.

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 parameters are well-documented in the schema itself. The description mentions 'compliance frameworks' and 'evidence documentation', which loosely map to 'framework' and 'includeEvidence' parameters, but adds no significant semantic details beyond what the schema provides. Baseline 3 is appropriate given high schema coverage.

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: 'Generate comprehensive audit reports for compliance frameworks with evidence documentation and findings.' It specifies the verb ('generate'), resource ('audit reports'), and scope ('compliance frameworks'), but doesn't explicitly differentiate from sibling tools like 'generate_html_report' or 'generate_professional_report' that might overlap in report generation functionality.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or exclusions, nor does it reference sibling tools that might handle similar report generation tasks. The agent receives no usage differentiation.

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