marketplace_export_data

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions exporting/downloading data but does not describe return format (e.g., file URL, base64), authentication requirements, or any processing behavior. This is a significant gap for a data export tool.

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 two short sentences, front-loads the core purpose, and contains no redundant information. Every word contributes to understanding the tool's function.

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?

There is no output schema, so the description should clarify what the agent receives (e.g., file content, download link). It does not, nor does it explain conditional requirements like 'target' being needed for certain export types. The description is too minimal for a tool with 4 parameters and no output specification.

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%, with each parameter (format, target, exportType, periodDays) having a brief description. The tool description adds little beyond the schema except naming CSV/JSON formats, so the baseline of 3 applies.

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 a specific action ('Export analytics data'), the resource (analytics data), and the output formats (CSV, JSON). It distinguishes this tool from sibling analytics/viewing tools by emphasizing 'download data' for external use, making its purpose unmistakable.

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 gives a clear use case ('Use this to download data for external analysis, reporting, or record keeping') but does not explicitly mention when not to use it or name alternative tools. It provides context without exclusions, earning a 4.

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