update_subscription_status

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

With no annotations, the description carries full burden. It explains that different statuses affect billing behavior (active = billing, paused = no billing, archived = ended). However, it does not disclose reversibility, permission requirements, or side effects on invoices or payments.

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?

Three sentences: first gives purpose and endpoint, second states required status, third lists meanings. Front-loaded and no unnecessary words.

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?

The tool is simple and the description covers the status meanings. However, no output schema is provided, so describing the return value or error conditions would improve completeness. Minor gap.

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 100%, baseline 3. The description adds value by explaining the meanings of each status value beyond the schema's brief description. For subscriptionId, no extra meaning is provided, but the status parameter is well-semantified.

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 a subscription status' with specific verb and resource, and lists the endpoint and status meanings. It distinguishes from siblings like delete_subscription by noting the 'archived' status as a preferred alternative.

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 provides explicit context for each status value (active, paused, archived, requestPayment) and indicates when to use 'archived' instead of delete. It does not fully contrast with update_subscription or other alternatives, but the guidance is clear enough.

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