Export compliance & traceability report

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

The description confirms the read-only nature noted in annotations ('Read-only'). It does not add significant behavioral context beyond what annotations already provide (no mention of performance, pagination, or side effects). For a read-only tool with good annotation coverage, this is adequate but not excellent.

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 somewhat dense but front-loads the main purpose and lists components efficiently. It could be slightly more concise, but every sentence adds value and no word is wasted. Structure is logical (purpose, components, formats, read-only note).

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 (merging multiple audit primitives) and lack of output schema, the description is remarkably complete. It enumerates all included data sources, the board-level summary, and the three output formats with their intended use cases. No critical gaps are apparent.

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?

The schema covers 80% of parameters with descriptions, but the description adds meaning beyond the schema by explaining that includeCommits affects speed ('faster') and that maxCommits limits linked commits. This provides practical usage context absent from the schema alone.

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 a specific verb ('export') and resource ('compliance & traceability report'), explicitly distinguishing it from sibling tools like get_ticket_history, get_work_log, and drift_report by positioning it as a 'unified' merge of those primitives. This makes the tool's purpose highly distinct.

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 clear context on when to use the tool: for an audit of one ticket or the whole board, with format options. It does not explicitly state when not to use it or name alternatives, but the context is sufficient for an agent to differentiate from granular sibling tools. Lacks exclusion guidance.

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