Get Subscriptions

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

Annotations already provide readOnlyHint=true. The description reinforces the read-only nature and explains filtering capabilities (status, date range, amount comparison, pagination), adding value beyond annotations. 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 front-loaded with the core purpose and a read-only indicator. It includes necessary security context but is slightly verbose. Overall, every sentence adds value.

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 read-only list tool with 9 optional parameters, the description covers all filter fields, pagination, and usage restrictions. The presence of an output schema reduces the need to explain return values, making this description complete.

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?

With schema description coverage at 0%, the description fully compensates by explaining the meaning and usage of all 9 parameters, including allowed values for status, amount_range comparison operators, and pagination fields.

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 'Retrieve subscriptions from Pine Labs', providing a specific verb and resource. It also explicitly marks the tool as read-only and official, distinguishing it from sibling tools like create_subscription or cancel_subscription.

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 includes explicit directives: 'All parameters are optional filters' and a security warning to only call when explicitly requested by the human user, preventing misuse. However, it does not explicitly differentiate from other subscription retrieval tools like get_subscription_by_id.

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