update-subscription

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, so the description builds on that by detailing the renewal action (body format, expiration extension). It does not contradict annotations. The tip adds behavioral context about timing.

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 and begins with the core purpose. The tip is helpful, but the first paragraph includes general context (e.g., 'The table in the Permissions section') that is not specific to the tool, slightly reducing efficiency.

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 presence of detailed annotations and a rich input schema, the description covers the essential purpose and key action. It omits details about includeHeaders/excludeResponse parameters, but those are auxiliary. No output schema needed. Overall, complete enough for a renewal tool.

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 75%, and the description repeats the key subfield (expirationDateTime) from the schema. The tip provides little additional meaning beyond what the schema already describes, so baseline of 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 'Renew a subscription by extending its expiry time', using a specific verb and resource. It distinguishes from sibling tools like create-subscription, delete-subscription, and reauthorize-subscription by focusing on renewal.

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 tip explicitly advises to 'Call before the current expirationDateTime to avoid missing notifications', providing clear usage timing. It also mentions checking docs for max extension. However, it does not explicitly exclude alternative tools or discuss when not to use.

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