Export report details

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful non-annotation fact — the required permission (view_reports) — but says nothing about output size, latency, or what happens when the row is missing.

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?

Only four sentences, but "Exports reports data" is pure restatement of the first sentence and "Export report details" restates the title. The one valuable fact (the permission) is buried at the end rather than front-loaded.

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?

An output schema exists, so return values needn't be explained, but for a 6-parameter tool whose name hinges on row-level vs report-level export, the description leaves the central distinction and the interaction between report_id and report_row_id unexplained.

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%, so the baseline would be 3, but the description's only parameter claim — that parameters "filter out exported data" — mischaracterizes format, response_format and verbose, which are output-shaping rather than filtering. It adds no meaning beyond the schema and slightly risks misleading the agent about report_id/report_row_id.

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 the verb and resource ("Export report details"/"Exports reports data"), but it never distinguishes this row-level export from the sibling action1_get_export_for_report and action1_report_export. An agent could not tell from the description alone that this exports a single report row rather than an entire report.

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?

"Use parameters to filter out exported data" is the only usage hint and it isn't a when-to-use rule. There is no mention of the near-identical siblings (get_export_for_report, report_export, list_report_data) or of the conditions that would select this one.

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