get_users_subscriptions

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

The description discloses read-only nature, pagination (20 per page), sorting order, AND operator for params, and behavior when page number exceeds maximum. Annotations confirm readOnlyHint, idempotentHint, and non-destructive nature, with no contradiction.

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 moderately concise, front-loaded with a summary line including read-only status and HTTP method. It contains no wasted words but could be slightly tighter.

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 explains the list behavior and parameter interaction but lacks details about the response structure (fields of each subscription). No output schema to rely on, so a slightly higher completeness would be beneficial.

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% with descriptions for each parameter. The description adds context about pagination and AND filtering, but does not significantly enhance individual parameter meaning beyond the schema.

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 it retrieves user subscriptions, specifying they are sorted by creation date descending and paginated. It distinguishes from sibling tools like get_subscription_plan or get_list_subscription_plans by focusing on user-specific subscriptions.

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 explains how to refine the list using query params with AND logic, but does not explicitly state when to use this tool versus alternatives. However, the context of user subscriptions is clear.

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