subscriptions.list

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

No annotations provided, yet description fails to disclose read-only nature, pagination behavior (implied by startsAfter/limit parameters), result ordering, or timestamp units. Absence of destructive behavior disclosure is critical gap for a financial API tool.

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?

Extremely brief (3 words) but underspecified rather than elegantly concise. Not front-loaded with critical behavioral constraints; presents as sentence fragment rather than structured guidance.

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?

Severely inadequate for a 5-parameter list operation with no output schema or annotations. Fails to explain pagination mechanics, result set characteristics, or timestamp filtering capabilities essential for correct invocation.

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% with 5 undocumented parameters including timestamp ranges and pagination cursors. Description provides zero compensation—no mention of Unix timestamps, cursor-based pagination, or filtering semantics.

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 basic action (List) and resource (Ryft subscriptions) but lacks specificity regarding scope or differentiation from sibling 'subscriptions.get' or 'subscriptions.getPaymentSessions'. Minimal viable description.

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?

No guidance provided on when to use this versus retrieving individual subscriptions via subscriptions.get, or how it relates to subscription management workflows. No mention of pagination strategy despite cursor parameters existing.

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