reports_export_data

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

Lacks annotations and description does not disclose behavioral traits such as permissions needed, side effects (e.g., file download), or rate limits. The agent cannot infer whether this is a simple read or triggers an export.

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?

Single sentence, no redundant information. However, the brevity sacrifices necessary detail; a bit more structure could improve completeness without losing conciseness.

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?

No output schema, no annotations, and the description is too minimal to fully inform the agent about what 'exportable report data' entails, the return format, or the relationship between optional sprintId and required dates.

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 50% (startDate and endDate have format hints). The description adds no extra meaning beyond the schema, but the schema itself handles half the parameters. Baseline 3 is appropriate given moderate coverage.

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 conveys the action (getting) and resource (exportable report data) and differentiates from sibling report tools that target specific report types like attention, global, project. However, 'exportable report data' is somewhat vague without specifying the scope or format.

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 other report-related tools (e.g., reports_project, reports_attention). No alternatives or prerequisites mentioned.

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