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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'leitura' is consistent with those. The description adds useful extra behavior by mentioning cursor-based listing and bulk execution via ids, though it does not explain response shape or other runtime behavior.

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 short and front-loaded with the read-only scope, and the action/parameter mapping is compact. The '[Flattened action: assets]' note is slightly cryptic, but the overall text is efficient and not padded.

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?

There is no output schema and no explanation of what 'assets' actually returns, which leaves an agent uncertain about the result. The description also introduces multiple actions while declaring only 'assets' as the flattened one, and it never explains the account parameter, making the tool incomplete for confident 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?

Schema description coverage is 0%, so the description must compensate. It does link cursor to list, id to get/assets/transactions, and ids to batched execution, which gives real meaning to several parameters. However, 'account' is left completely unexplained, so the compensation is incomplete.

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 says this is read access to Guru affiliations and identifies 'assets' as the flattened action, so it goes beyond a tautology. However, the action list 'list/get/assets/transactions' muddles what this specific tool does, and 'assets' is never defined, making the purpose less crisp than it could be.

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 no explicit guidance about when to use this tool instead of sibling tools like guru_affiliations_get, guru_affiliations_list, or guru_affiliations_transactions. The mention of cursor and bulk support hints at usage, but it does not give selection criteria or exclusions.

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