export_data

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions format dependencies (xlsx requires openpyxl) but omits critical details such as where files are saved, whether they overwrite existing files, authentication requirements, or the return value (despite an output schema existing). The description fails to convey important side effects and limitations.

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 extremely concise: two sentences that front-load the purpose and then list the formats. Every sentence earns its place with no filler or redundancy.

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?

Given the tool's simplicity (3 parameters, all documented in schema), the description is minimally adequate. It explains formats and data sources but lacks details about file path, overwrite behavior, and permissions. The presence of an output schema is unmentioned. Overall, functional but with gaps.

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 100%, so the baseline is 3. The description adds context for the format parameter by explaining format characteristics ('csv universal, json API-friendly, xlsx requires openpyxl'), which adds value. However, it does not enrich the data or filename parameters beyond what the schema provides. Overall, moderate added value.

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 purpose: 'Save data from get_resource_data() or transform_data() to file.' It specifies the verb 'Save' and the resource 'data to file', and it distinguishes from sibling tools like export_visualization (which exports charts) and export_chart_pdf (which exports PDFs of charts).

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 does not provide any guidance on when to use this tool versus alternatives. It mentions data sources but lacks explicit when-to-use or when-not-to-use instructions. No alternatives are named, and there is no context about excluding other export tools.

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