Get transactions

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

Beyond the readOnly/idempotent annotations, the description discloses a real API quirk (product_id silently returns rows for other products), defines matching semantics as case-insensitive contains on item_name, and explains fetch_all pagination behavior. 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?

Three dense sentences with no filler. The first sentence states the core purpose, and the following sentences provide high-value caveats and usage constraints without redundancy.

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 read-only retrieval tool with no required parameters and full parameter documentation, the description covers the important edge cases: filter reliability and fetch_all behavior. The lack of an output schema is acceptable because the returned resource is unambiguously transactions and the description provides enough for correct 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 already documents all 8 parameters with 100% coverage, so baseline is 3. The description adds semantic value by warning against ThriveCart's product_id filter and steering the agent to item_name as the reliable filter, which is not captured in any schema field.

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?

States a specific operation and resource: 'Get transactions from a ThriveCart account', and names the filtering dimensions. The verb-resource pair clearly differentiates it from sibling list/get tools even without explicit exclusions.

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?

Gives concrete usage guidance: 'Set fetch_all only when you need complete figures; it walks every page' and instructs using item_name because product_id is unreliable. It does not name sibling alternatives explicitly, but the context and API warnings are clear enough.

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