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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description reinforces 'leitura'. It adds useful behavioral context through 'Bulk support' and the action inventory, but it does not disclose other traits such as authentication requirements, rate limits, or response shape. With strong annotations, this 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 well-structured: read-only summary, action list, flattened-action note, and bulk support. The 'Flattened action: invoices' phrase is somewhat cryptic and not fully explained, which prevents a 5, but the overall layout is efficient and scannable.

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 tool with 15 optional parameters, no output schema, and multiple bundled actions, the description provides a decent parameter-to-action map and bulk guidance. However, it lacks clarity on what the 'Flattened action: invoices' actually returns, does not explain every parameter (e.g., account), and assumes familiarity with the granular subscription tools.

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%, but the description compensates by mapping parameters to specific actions (e.g., 'get (id)', 'invoice (id + invoice_code)', search filters) and by noting that ids/product_ids enable batched execution. It does not explain every parameter (notably 'account'), but the provided action/filter mapping adds meaningful semantics beyond raw schema names.

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 the resource ('Assinaturas no Guru') and the read-only nature, and enumerates concrete sub-actions (search, get, invoices, invoice, transactions, etc.). It does not explicitly differentiate this aggregate tool from granular siblings like guru_subscriptions_search or guru_subscriptions_invoice, so it stops short of a 5.

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 provides clear usage context by listing available actions and their expected filters, and highlights bulk execution support via 'ids, product_ids'. However, it does not explicitly state when to use this tool instead of the individual guru_subscriptions_* sibling tools, so it lacks explicit exclusions/alternatives.

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