List EDD Sales

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

No annotations provided, so description has full burden. Describes tool as listing 'recent' sales but does not define 'recent', default sort order, pagination behavior, or any side effects. Lacks important behavioral details.

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?

Single concise sentence that communicates purpose and primary capability. No unnecessary words, but could be structured with more detail without losing conciseness.

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?

Tool has 5 parameters and no output schema. Description does not explain default return count (number param default 10), pagination details, or output format. Incomplete for an effective agent 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?

Input schema has 100% description coverage, so baseline is 3. Description adds that filtering is 'optional', but does not provide additional semantics beyond schema descriptions.

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?

Clearly states action 'list', resource 'sales/transactions', and optional filters by email or date range. Distinguishes from sibling tools like 'edd_get_sale' (single sale).

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 this versus alternatives. For example, does not mention that 'edd_get_sale' is for a single sale. No context on prerequisites or default behavior.

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