exportFixItemsCsv

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds useful behavioral context: the CSV is returned as text, can be consumed programmatically, and represents one row per proposed change. This goes beyond what the annotations alone express.

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?

Two short sentences with no wasted words. The first sentence states the core operation and format; the second explains what can be done with the output and adds the PDF limitation. It does not repeat schema fields or annotation information.

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?

For a single-parameter, read-only export tool, the description covers everything needed to invoke it correctly: the required auditId is in the schema, the response format is stated as CSV text, and the PDF limitation is explicit. An output schema is present, so detailed return structure does not need to be duplicated here.

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 only parameter, auditId, is fully documented in the input schema with 100% coverage. The description does not add further detail about the parameter, but the schema already carries the semantic burden. This is the appropriate baseline case.

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 names the exact verb ('Export'), resource ('an audit's fix list'), and format ('as CSV'), and adds the semantic 'developer-handoff format, with one row per proposed change.' This distinguishes it from sibling listFixItems and other audit-related tools. The CSV-vs-PDF caveat further disambiguates what this tool produces.

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?

It clearly communicates the use case: obtain a machine-readable CSV fix list that can be read, transformed, or written to a file. It also gives an exclusion by stating that PDF export is dashboard-only. It does not explicitly name an alternative sibling tool, but the CSV-versus-PDF distinction is sufficient routing guidance.

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