fo_export_report

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

Description implies read-only operation ('Export') and return format (CSV text). No annotations exist, so description provides basic transparency but omits details like permissions, rate limits, or side effects.

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?

Two sentences, no redundant words, front-loaded with purpose. Every word adds value.

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 no output schema, description states return format (CSV text). However, it doesn't clarify that output format can be changed via ReportFormat parameter, potentially misleading if user selects EXCEL or XML. Otherwise adequate for a simple export tool.

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%, and description adds no new meaning beyond mapping 'clicks, approved sales, pending sales' to ReportType and 'date range' to date parameters. Baseline score 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?

Description clearly states verb 'Export' and resource 'performance report', specifies data types (clicks, approved sales, pending sales), and indicates output format. Distinguishes from siblings like fo_count_products or fo_get_payment_details.

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 explicit guidance on when to use or when not to use, nor comparison to siblings. Implies usage for generating performance reports but lacks context like prerequisites or typical scenarios.

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