subscriptions_list

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the read-only nature. The description adds the return shape ({subscriptions:[...], count}) and the SKU scoping, which goes beyond the annotations without contradicting them.

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 extremely concise, with only two sections: purpose and return. Every sentence is informative and front-loaded, with no redundancy or filler.

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?

For a simple list operation, the description provides the essential purpose and return shape. Annotations and schema cover safety and parameters, so the description is complete enough. It doesn't mention pagination, but the schema's limit/after/before parameters implicitly cover that, and an output schema exists.

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 80%, so most parameters are already described in the schema. The description adds no additional parameter context, which is acceptable since the schema carries the burden. No param info is provided in the description, so a baseline 3 is appropriate.

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 'List subscriptions for a SKU,' which is a specific verb and resource. It distinguishes this tool from siblings like subscriptions_get (single subscription) and entitlements_list (different resource).

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?

The purpose statement implies when to use the tool (listing subscriptions for a SKU), but it does not explicitly mention alternatives or exclusion criteria. No guidance is provided on when to use another tool like subscriptions_get instead.

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