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

Annotations indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, which are consistent with read operations. However, the description itself is inconsistent (listing multiple actions) and does not clarify the exact behavior (e.g., whether it returns usage data only or all subscription data). The bulk support hint is useful but insufficient.

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 bullet-point structure helps readability, but the description includes extraneous actions (list, get, items, cycles) that are not directly relevant to the tool's stated flattened action of 'usages'. This reduces conciseness and could be trimmed.

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 8 parameters, no output schema, and no schema descriptions, the description lacks critical details about return values, the data parameter format, and how bulk execution works. The agent would have difficulty using this tool correctly without additional information.

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 adds some meaning by linking parameters to specific actions (e.g., subscription_id for get, item_id for usages). It also mentions bulk support with subscription_ids and item_ids. However, the mapping is incomplete and the data parameter is only loosely described.

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) and then says '[Flattened action: usages]', creating confusion about the tool's actual purpose. It does not clearly state that this tool is specifically for querying usages of a subscription item, and the inclusion of unrelated actions undermines clarity.

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 explicit guidance on when to use this tool versus sibling tools like pagarme_subscriptions_list, pagarme_subscriptions_get, pagarme_subscriptions_items, or pagarme_subscriptions_cycles. The description mentions bulk support but does not help the agent decide when to choose this tool over alternatives.

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