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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description echoes the read-only nature. It adds useful context about batched execution via ids/marketplace_ids/product_ids/subscription_ids, but it does not disclose response shape or cursor/page behavior. No contradiction with the annotations exists.

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 compact, front-loaded with the read intent, and organizes actions and filters into readable groups. The bulk support note is concise and the overall length is appropriate for the number of mentioned parameters, though it is dense.

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?

Given no output schema and 20 loosely typed parameters, the description provides enough action/filter mapping to invoke the tool in basic cases. It lacks clarification of how this flattened tool relates to sibling transaction read tools, which could make selection ambiguous for an AI agent.

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 0%, so the description has to carry parameter meaning, and it partially does by grouping filter parameters, date format YYYY-MM-DD, cursor, and bulk array parameters. Several parameters such as `account` and some action relationships are left under-explained, so it only partially compensates for the schema gap.

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 states this tool is for reading Guru sales/transactions and enumerates the supported actions (search, get, activities, order_bumps, etickets, by_marketplace), so the core purpose is clear. It does not explicitly contrast itself with sibling transaction-read tools like guru_transactions_search, but the resource and read intent are specific enough.

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 includes action-based usage hints: filters map to search, id-based operations map to get/activities/etickets, and bulk support is explained. It gives no explicit guidance about when to choose this tool over the many sibling transaction tools, so the agent must infer the right context.

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