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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description reinforces this with 'leitura'. It adds useful context about bulk execution and the flattened search action, but it does not disclose pagination behavior, response shape, or how cursor should be used, so transparency is adequate but not rich.

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 and front-loaded with the read-only purpose, but it packs multiple action names and a 'Flattened action: search' note into a dense block. Several listed actions belong to sibling tools, so those parts are confusing and do not earn their place in this tool's description.

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?

This is a complex 20-parameter tool with no output schema and no parameter descriptions in the schema. The description covers many filter names and bulk support, but it omits important operational details such as cursor pagination, valid transaction_status values, the meaning of 'account', and what the search response contains. It is not complete enough for reliable 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?

With 0% schema description coverage, the description carries the burden of explaining parameters. It does a decent job by naming most filters and specifying the YYYY-MM-DD format for date fields, plus sub enum values and bulk array parameters. However, 'account' is left unexplained and some parameter semantics are only implicit.

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 this is a read-only tool for Guru sales/transactions and centers on the 'search' action with filters. However, it lists get/activities/order_bumps/etickets/by_marketplace actions that correspond to separate sibling tools, so it does not cleanly distinguish this tool's scope.

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 implies usage through 'search' and filter lists, but it gives no explicit guidance on when to choose this tool over sibling tools like guru_transactions_get or guru_transactions_activities. In fact, by listing those actions inside this tool's description, it actively blurs the boundary between this search tool and its siblings.

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