sigma_export_report

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description adds no behavioral context about what happens after export (e.g., returns content, creates a file, triggers a download). It does not mention permissions or side effects, leaving the agent to infer behavior.

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 very short and front-loaded with the action. The list of formats is directly useful. However, it reads more like a parameter note than a well-structured description, and it sacrifices necessary details for brevity.

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 simple export tool with only two parameters, the description is still incomplete. It fails to clarify the return type or output behavior (critical for an export), lacks guidance on how to specify the report, and offers no context about alternative tools. The presence of an output schema helps but does not cover usage context.

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 has 0% description coverage, so the description must compensate. It lists the allowed format values ('pdf', 'png', 'csv', 'xlsx'), which helps, but provides no explanation of what report_id refers to or how it should be formatted. The parameter meaning is only partially addressed.

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 action 'Export a report' with a specific resource. It does not differentiate from sibling tools like sigma_export_workbook or sigma_export_and_download, but the core purpose is unambiguous.

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 given on when to use this tool versus alternatives. There is no mention of prerequisites, context, or situations where another export tool would be preferred.

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