ls_update_subscription_item

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

Annotations already indicate destructiveHint=true and idempotentHint=true, which the description aligns with but does not elaborate on. The description adds no further behavioral detail (e.g., proration, billing cycle impact). With annotations covering basic traits, the description adds minimal extra transparency.

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 concise: two short sentences that front-load the primary action. No extraneous words. Could be slightly more compact by merging, but current form is efficient.

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 two-parameter mutation tool, the description provides the core purpose but lacks details on consequences (e.g., proration, invoice generation) or return value. Given no output schema, a note on return could help. The context is sufficient but not fully complete.

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 100%, with both 'subscriptionItemId' and 'quantity' described clearly. The description does not add any parameter-related information beyond the schema. Baseline score of 3 is appropriate as the schema handles param semantics.

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 states 'Update a subscription item's quantity' with specific use case 'seat-based or quantity-based billing', clearly identifying the action and resource. Among siblings like ls_update_subscription and ls_cancel_subscription, this tool is uniquely focused on quantity updates, providing clear distinction.

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 description mentions 'Used for seat-based or quantity-based billing', giving context on when to apply. It does not explicitly exclude other scenarios or mention alternatives, but the context is clear enough for an agent to decide. A slight deduction for lack of explicit exclusions.

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