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

Annotations declare readOnlyHint=true and idempotentHint=true, which are consistent with listed read-only actions. However, the description fails to explain how the 'flattened action' mechanism works; there is no action parameter in the schema, so an agent cannot determine how to trigger a specific action. The behavioral contract 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 moderately concise but structurally flawed: it lists multiple actions under a single tool name without clear hierarchy, and the 'flattened action' note is cryptic. It could be more focused and better organized.

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 complexity (8 parameters, no output schema, no action-selection parameter), the description is incomplete. It does not explain the 'flattened action' concept or how an agent should invoke a specific action. The tool's behavior remains ambiguous, especially with the inclusion of actions that have dedicated sibling 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?

Description adds meaning to many parameters beyond the input schema (which has 0% coverage). It maps page, size, data for 'list'; subscription_id for 'get', 'items', 'cycles'; item_id for 'usages'; and mentions bulk support using subscription_ids and item_ids. The 'data' parameter is partially described. Only the 'account' parameter is not covered.

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 tool name is 'pagarme_subscriptions_cycles' but the description lists multiple actions (list, get, items, cycles, usages), making it unclear what the tool actually does. It does not specify that this tool is specifically for cycles, and the presence of other actions that have separate sibling tools (e.g., pagarme_subscriptions_get) adds confusion.

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 on when to use this tool versus alternatives. The description does not indicate which action to invoke or how to select between the listed actions, nor does it explain when to use this tool over other subscription-related sibling tools.

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