generate_compliance_evidence

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

No annotations are present, so the description must fully disclose behavior. It does not mention side effects, output format, or any long-running nature. The agent cannot infer whether the bundle is generated as a file, returned inline, or if there are any rate limits or destructive actions.

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 conveys the core action and object. It is concise but could be slightly less terse. It earns its place with clear front-loading of key terms.

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 lack of output schema and the presence of many sibling tools, the description is inadequate. It does not explain what the bundle contains, how to access the result, or any post-generation steps. For a generation tool, this is a significant gap.

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%; the single parameter 'framework' has a clear description and enum values. The description adds no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

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 'Generate auditor-ready compliance evidence bundle for a framework' clearly states the verb (generate) and resource (compliance evidence bundle). It specifies that the bundle is for a framework, and the enum parameter lists the frameworks. However, it does not differentiate from sibling tools like 'compliance_gap_analysis' or 'compliance_posture', which have distinct purposes.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, recommended scenarios, or exclusion criteria. Given multiple compliance-related siblings, explicit usage context is needed.

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