reauthorize-subscription

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

Annotations already mark as destructive and open-world; description adds that no body is required and emphasizes the time-sensitive nature to avoid expiry. This builds trust and sets expectations without contradicting 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?

Two sentences plus a tip. Every part is meaningful and front-loaded with the purpose. No redundancy or fluff.

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 simple mutation tool with no output schema, the description covers purpose, trigger, and critical timing. Could optionally mention what the response looks like, but the schema's optional parameters give some control.

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% and parameter descriptions are clear. The description adds no additional meaning beyond the schema, which is acceptable. The note about 'no body required' is helpful but not param-specific.

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 upon a reauthorizationRequired challenge, which is distinct from sibling tools like create-subscription or delete-subscription. The trigger and action are unambiguous.

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?

Specifies the exact scenario (reauthorizationRequired challenge) and provides a crucial usage constraint (must be called within 48h window). Lacks explicit exclusion of other use cases but the context is sufficient for the specific trigger.

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