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

Annotations already show readOnly and idempotent. The description adds bulk support (accepting subscription_ids and item_ids) and parameter requirements for actions. However, the multi-action description introduces confusion about which behaviors apply to this specific tool.

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 cluttered with multiple actions and the cryptic '[Flattened action: items]'. It could be more concise by focusing solely on the items action, which would improve clarity.

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 8 parameters and lack of output schema, the description should clarify the tool's specific behavior (items) and how parameters like item_ids and pagination work. The current description is incomplete and ambiguous.

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 coverage is 0%, so the description must compensate. It relates parameters to actions (e.g., subscription_id for items), but includes irrelevant parameter-to-action mappings for list and get, which are not part of this tool's intended scope.

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) while the tool name and annotations indicate it should be specifically about subscription items. The 'Flattened action: items' hint is ambiguous, making the primary purpose unclear.

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 vs siblings like pagarme_subscriptions_list or pagarme_subscriptions_get. The inclusion of list and get actions here could mislead an agent into using this tool for those purposes instead of the dedicated tools.

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