gumroad_get_sales

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

The description explicitly says 'Reads money without moving it,' which usefully discloses that this is a read-only operation with no side effects. However, with no annotations provided, the description still omits important behavioral details like pagination mechanics via page_key, whether results are ordered, or how date filters behave on output.

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 appropriately brief and front-loaded: it states the output shape first, then the safety behavior. The 'Operation id' line is slightly internal but still compact and informative. No wasted words, though the sentence fragment 'Sales, one row each' could have been written as a fuller sentence.

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?

For a tool with no output schema and no annotations, the description does not provide enough context for reliable invocation. The agent is not told how pagination works, what output fields to expect, whether filters are mutually exclusive, or how this relates to gumroad_get_sales_summary. Several parameters remain unexplained across both the schema and description.

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 only 60%, leaving page_key and product_id undocumented in the schema. The description itself adds no parameter-level meaning, so it does not compensate for that gap. It also does not clarify how after and before interact or what granularity 'one row each' implies relative to the available filters.

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's 'Sales, one row each' clearly indicates this tool returns individual sale records rather than an aggregate, and 'Reads money' clarifies it is a read operation. Combined with the tool name get_sales, this is enough to identify the tool's purpose. It does not use an explicit verb like 'get' or 'list', but the operation id 'listSales' reinforces the meaning.

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 about when to use this tool versus its siblings, especially gumroad_get_sales_summary. The description does not mention alternatives, exclusions, or the appropriate context for choosing this over other sales-related tools.

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