analytics_revenue

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

No annotations are provided, so the description carries the burden. It discloses that the report includes period comparison and daily breakdown, but does not mention return format, pagination, or explicit read-only behavior. As a report tool, the read-only nature is implied but not stated.

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, well-front-loaded sentence with no redundant information. It immediately states the tool's purpose and key features.

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?

With no output schema, the description only partially explains the report's content. It covers the core purpose but lacks detail on response format, data granularity beyond daily, or how to choose between predefined and custom periods. A bit more context on use cases would improve completeness.

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 all parameters are well-documented. The description adds no new parameter semantics, merely restating the compare_previous feature (already in the schema) and adding the non-parameter 'daily breakdown' output detail.

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 generates a revenue report, with specific features (previous period comparison and daily breakdown). This distinguishes it from sibling analytics tools like analytics_top_products or analytics_avg_order.

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 implies usage for revenue reporting but does not explicitly state when to use this tool versus alternatives like analytics_dashboard or analytics_by_channel. No exclusion or alternative guidance is provided.

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