refresh_subscription

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

Annotations declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the agent already knows this is an irreversible mutation. The description usefully adds the edition/license/permission gating and the 404/empty-list failure modes, but never says what 'refresh' actually mutates or what state gets replaced.

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 short sentences, front-loaded with the action, followed by the caveat and the route. Slightly telegraphic phrasing ('refresh subscription.' lowercase fragment) but no wasted text.

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 call with no inputs and no output schema, the main missing piece is the effect: what changes after a refresh and how the caller can tell it succeeded. The availability and 404 caveats are a genuine plus, but the core mutation is left opaque.

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?

Zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. Baseline of 4 applies.

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?

States a specific verb+resource ('refresh subscription') and grounds it with the underlying route POST /subscription/refresh, which distinguishes it from get_subscription, activate_subscription, and delete_subscription. It does not explicitly contrast with activate_subscription, which is the nearest ambiguous 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 availability caveat (edition/license/permissions, possible 404 or empty lists on Community) gives useful context for when the call can succeed, but nothing says when to prefer refresh over activate_subscription or get_subscription. Usage is implied rather than directed.

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