reauthorize-subscription

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

Annotations mark destructiveHint: true, lowering the disclosure bar. The description adds genuinely useful context beyond the annotations: the 48h window, the lifecycle trigger, and the 'no body required' note. It does not explicitly describe timing side effects on expiry, but it goes beyond what annotations declare. No contradiction with the destructiveHint annotation.

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 core action is front-loaded, and the text is short. However, there is noticeable redundancy: the TIP's first clause ('Reauthorizes a subscription after receiving a reauthorizationRequired lifecycle notification') nearly repeats the main description verbatim. The genuinely useful additions (48h window, no body required) could have been merged into a single tighter paragraph.

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 tool with a single required parameter, full schema coverage, and a destructiveHint annotation, the description covers the key operational facts: the trigger condition, the time window, and that no body is required. Absent an output schema, return-value behavior is not specified, but this is not critical for a simple reauthorization call. Reasonably complete for its complexity.

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%, so the schema already documents all four parameters thoroughly, including the helpful guidance on how to pass subscriptionId (not as 'id'). The description adds 'no body required' but little parameter-specific meaning beyond what the schema supplies. Baseline 3 is appropriate given full schema coverage.

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 a specific verb (reauthorize) and resource (subscription), and ties it to an explicit trigger: the 'reauthorizationRequired challenge' / lifecycle notification. This clearly distinguishes it from sibling tools like create-subscription, delete-subscription, and update-subscription by its unique trigger condition.

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 clearly states when to use the tool — upon receiving a reauthorizationRequired lifecycle notification — and adds a timing constraint (within the reauthorizationRequiredDateTime window, typically 48h). It doesn't explicitly name alternatives or state when-not-to-use, but the trigger is specific enough that the usage context is unambiguous.

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