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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description consistently states 'leitura' (reading). The description adds useful context about bulk support (ids, product_ids) and lists filters. However, it doesn't disclose specifics like pagination behavior or what each action returns, which would be valuable beyond the annotations.

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 a single dense paragraph with a list of actions and parameters. It's informative but not well-structured; the 'Flattened action: activities' note is cryptic. It could be organized with clearer sections or bullet points, and the opening is concise but the rest feels cluttered.

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?

With 15 parameters, no output schema, and no required fields, the description should clarify what each action returns and how to use them. It lists actions and filters but does not explain return values, pagination (though cursor is mentioned), or when to use each action. The lack of guidance on action selection is a significant gap.

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 map action types to parameters (e.g., search uses filters, get uses id, invoice uses id + invoice_code) and mentions bulk support with ids and product_ids. This adds meaning beyond the raw schema, but it does not explain parameter formats or constraints, leaving some ambiguity.

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 it's about subscriptions in Guru (read-only), but the tool name includes 'activities' and the description lists many actions (search, get, activities, invoices, etc.), making it ambiguous whether this tool is specifically for activities or a general subscription reader. It does not clearly distinguish from sibling tools like guru_subscriptions_get or guru_subscriptions_search.

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?

No guidance is provided on when to use this tool versus the many sibling tools (e.g., guru_subscriptions_get, guru_subscriptions_invoices, guru_subscriptions_transactions). The description lists actions but does not explain when to prefer this tool over dedicated ones, nor does it describe exclusions or prerequisites.

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