fiken_create_product_sales_report

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

The description does not disclose behavioral traits beyond what the annotations provide. Annotations indicate readOnlyHint=false, implying mutation, and the description says 'Creates', which is consistent. However, it lacks details about what happens when the report is created (e.g., is it saved? returned? what format?). No contradiction with annotations.

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 a single concise sentence that is front-loaded with the core action. No unnecessary words or repetition.

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?

The description is too brief for a report creation tool. It does not mention required parameters, output behavior, or what the report contains. Given the 4 parameters and no output schema, more context is needed for an AI agent to understand the tool's full purpose and invocation.

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?

The input schema covers 75% of parameters with descriptions (to, from, includeZeroValues). The description adds no additional meaning beyond the schema, and the missing projectId parameter is left undescribed. With high schema coverage, the description meets the baseline but does not compensate for gaps.

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 'Creates' and resource 'product sales report' with a scope 'for a date range', which is clear. However, it does not differentiate from sibling tools like fiken_create_sale or reporting tools, as there are no other report creation tools listed among siblings.

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 is provided on when to use this tool versus alternatives. The description only mentions 'for a date range' but does not specify scenarios, prerequisites, or exclude cases. Sibling tools include many sales-related operations, but no explicit when-to-use or when-not-to-use advice.

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