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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds context about bulk execution via subscription_ids and item_ids, and notes required parameters for each action (e.g., subscription_id required for items). However, it does not detail error behavior or return format, and the 'Flattened action' comment is unclear.

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 well-organized with bullet points for actions and parameters. It front-loads the general topic ('Assinaturas no Pagar.me V5') and efficiently lists actions. Slightly wordy but not excessive.

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 lack of output schema, the description covers required parameters for each action and bulk support. However, it does not clarify the return values or how the 'Flattened action: get' affects the main workflow. The presence of multiple actions in one tool without differentiation from siblings reduces completeness.

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 compensates by explaining the roles of page, size, data fields (customer_id, plan_id, status, created_since/until), subscription_id, item_id, and the bulk arrays. This adds significant meaning beyond the bare schema.

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 lists multiple actions (list, get, items, cycles, usages) but the tool is named 'pagarme_subscriptions_get' with a note 'Flattened action: get'. This creates ambiguity about the primary purpose. It is not clear whether this tool is for getting a single subscription or performing multiple read operations, especially since siblings like pagarme_subscriptions_list exist.

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 over sibling tools like pagarme_subscriptions_list, pagarme_subscriptions_items, pagarme_subscriptions_cycles, or pagarme_subscriptions_usages. The description does not explain the trade-offs or preferred contexts for the actions.

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