suppliers_export_csv

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

No annotations are provided, so the description must carry the burden. It discloses the return format (base64-encoded UTF-8 CSV with BOM) which is useful. However, it doesn't disclose that this is a data-reading operation versus destructive, doesn't mention rate limits, data volume implications, or that the CSV may need decoding by the caller.

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 sentences, zero waste. States the action, scope, and return format efficiently. Front-loaded with the primary purpose.

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?

The tool has 1 optional param, no output schema, and no annotations. The description covers purpose and output format but lacks behavioral context (e.g., how many records returned, pagination or truncation concerns, whether results are large enough to require download handling). For a simple export with a well-described single param, this is adequate but not rich.

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% for the single companyId parameter, which is well described as 'Company UUID (overrides configured default)'. The description mentions 'active company' which adds context that the default company is the active one, consistent with the override semantics. The description adds modest value beyond the schema.

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 states a specific verb (export) + resource (all suppliers) + scope (active company) + output format (CSV). It clearly distinguishes from siblings like suppliers_export_saga_xml (different format) and invoices_export_csv (different resource).

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 clearly implies it exports all suppliers for the active company, which creates a sensible default context. However, it does not explicitly address when-not to use it (e.g., for filtered exports, saga XML format, or clients vs suppliers), nor does it name alternatives like clients_export_csv or suppliers_export_saga_xml.

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