Get EDD Stats by Date Range

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only describes the tool's purpose without mentioning any behavioral traits such as data aggregation, return format, or potential side effects. For a read operation, the description should at least confirm it is non-destructive.

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 with no unnecessary words. It is front-loaded and efficient, though it may sacrifice completeness for brevity.

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 tool has three parameters, one enum, and no output schema. The description fails to explain the return structure (e.g., whether it returns daily breakdowns or totals). Given the absence of output schema and annotations, the description is incomplete for an agent to fully understand the tool's behavior.

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%, with each parameter having a description in the schema. The tool description adds minimal additional meaning beyond restating type and date range. It does not clarify date format nuances or provide examples, but the schema already handles this adequately, resulting in a baseline score of 3.

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 retrieves daily earnings or sales statistics for a custom date range. It specifies the resource (stats) and verb (get), and mentions the key parameters, distinguishing it from sibling tools like edd_get_stats_by_preset or edd_get_stats_by_product.

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 provides no explicit guidance on when to use this tool versus its siblings, such as edd_get_stats, edd_get_stats_by_preset, or edd_get_stats_by_product. It lacks any 'when to use' or 'when not to use' context, leaving the agent to infer usage solely from the name and parameter differences.

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