update_subscription

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

With no annotations, the description carries full burden. It implies mutation ('update') but provides no details on idempotency, permissions, partial failure behavior, or side effects like proration. The example only hints at seat changes.

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 a single concise sentence, which is efficient. However, it could be slightly expanded with minimal additional context without becoming verbose.

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 no output schema, the description does not explain return values or success conditions. It also lacks preconditions (e.g., subscription must be active) and does not address how this fits with sibling tools like 'get_subscription' or 'cancel_subscription'.

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?

Input schema coverage is 100% with clear descriptions for subscription_id and items, including nested fields. The description adds marginal value by giving an example of units as seats, but it does not explain item id or array semantics beyond the 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 clearly states 'Update subscription' with an example 'change number of seats/units', which specifies the verb and resource. It distinguishes from siblings like 'cancel_subscription' but could differentiate better from 'upgrade_subscription', which might imply a specific type of update.

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. There is a sibling 'upgrade_subscription' that could be confused; the description does not explain when to use update over upgrade or other sibling tools.

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