export_report

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

With no annotations, the description must fully disclose behavior. It states that 'bytes are written to save_path', indicating a file write side effect, but lacks details on overwrite behavior, permissions, size limits, or whether the tool returns a success indicator.

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 concise sentence that conveys the main purpose and key parameter values. However, it could be better structured (e.g., listing parameters) for readability.

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?

With 6 parameters (5 required) and no output schema, the description fails to document the required date_range parameters and the return value. It also doesn't mention that date_range is mandatory or how it affects the export.

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 0%, so the description must compensate. It explains valid values for report_type and fmt, and the purpose of save_path, but says nothing about the required date_range_start, date_range_end, or optional workspace_id, leaving crucial parameters unexplained.

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 function: exporting a report as a file with specific formats (PDF/CSV/XLSX) and report types (detailed/summary/weekly/attendance/expenses). It differentiates from sibling 'generate_*' tools by using the verb 'export', but does not explicitly contrast with them.

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 on when to use this tool versus alternatives (e.g., generate_* tools). It lists possible values for report_type and fmt, but does not provide context or exclusions.

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