update_media_subscriptions_by_subscription_id_move

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

The description adds behavioral detail beyond annotations by clarifying that if 'after' is missing, the subscription is inserted at the beginning of the list. This is useful context that complements the idempotent and non-destructive hints already present in the annotations. No contradiction with 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 compact and front-loaded with 'Re-order a subscription.' The HTTP line and Args list are directly relevant, and there is no fluff. It could omit the HTTP endpoint, but it adds useful context without significant bloat.

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 two-parameter operation with an output schema, the description adequately covers the action, target resource, and parameter behavior. It does not discuss return values (covered by output schema) or edge cases, but the tool is straightforward and the essentials are present.

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 0%, but the description fully explains both parameters: subscription_id identifies the subscription, and after specifies the subscription to move this one after, with a clear fallback to the beginning if omitted. This compensates entirely for the missing schema descriptions.

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 and resource: 'Re-order a subscription.' The HTTP endpoint /move and the distinction from the sibling update_media_subscriptions_by_subscription_id make the tool's specific role clear without needing to inspect schemas.

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?

Usage is implied by the operation name and the 'after' parameter explanation, but the description gives no explicit guidance on when to use this tool versus alternatives like update_media_subscriptions_by_subscription_id or delete_media_subscriptions_by_subscription_id. There is no when-not or alternative routing.

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