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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to restate safety. It adds the useful 'bulk support' behavior and 'leitura' context, but it does not describe output, scope, endpoint semantics, or what happens when using account. It is consistent with the annotations, so there is no contradiction.

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 text is short and front-loaded with 'leitura,' but the inclusion of a four-action list followed by '[Flattened action: transactions]' is redundant and slightly confusing. It earns some conciseness credit but not full marks because not every phrase adds clarity.

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 the 0% schema coverage, no output schema, four parameters, and a large family of similar transaction tools, this description does not provide enough context for an agent to confidently invoke the tool. It lacks clear semantics for transactions, account, return values, and relationships to alternative affiliation/transaction endpoints.

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 must clarify meaning beyond bare schema properties. It does partially: cursor is connected to list, id to get/assets/transactions, and ids to bulk execution. However, the account parameter is never explained, and the exact roles of the action parameters remain unclear.

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 identifies the resource broadly ('Afiliações no Guru (leitura)') and points to 'transactions' as the flattened action, so the domain is somewhat clear. However, it never states a concrete operation like 'retrieve transactions for an affiliation,' and the action list 'list (cursor); get (id); assets (id); transactions (id)' blurs whether this is a single-purpose transactions tool or a multi-action resource.

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?

There is some usage signal: action-to-parameter mappings are given (cursor for list, id for get/assets/transactions), and bulk execution is indicated by 'accepts ids.' But nothing says when to choose this over related sibling tools such as guru_transactions_search, guru_contacts_transactions, or guru_subscriptions_transactions, so the tool lacks strong disambiguation.

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