reauthorize-subscription

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

Annotations already indicate destructiveHint=true (mutation). The description adds that no body is required and must be called within a time window. It does not elaborate on side effects, error conditions, or return behavior, but the added time window context provides useful behavioral insight beyond annotations.

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 highly concise with two sentences and a tip. It is front-loaded, stating the core purpose, then adding a critical tip. Every sentence adds value without redundancy.

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 description is complete for a single-purpose reauthorization tool with a clear trigger and constraint. It provides enough context given the lack of output schema and the presence of sibling subscription tools. It could mention expected response or failure modes but is generally sufficient.

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%, so parameters are documented. The description adds no additional parameter-specific information beyond the schema. It mentions 'no body required', which is inferred from the schema having no required components beyond subscriptionId.

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 the tool reauthorizes a subscription specifically when a 'reauthorizationRequired' challenge is received. It distinguishes itself from other subscription tools (create, update, delete) with its unique trigger.

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 explicitly states when to use the tool (upon receiving a reauthorizationRequired challenge or lifecycle notification) and includes a critical timing constraint (48h window). However, it does not mention when not to use it, such as for normal subscription updates.

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