get_subscriptions

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

With no annotations, the description provides useful behavioral context: it notes the operation is 'readonly-owner' indicating permission level and safety, and it sets a limit of 1000 IDs, which is a rate/usage constraint. However, it does not detail behavior on invalid IDs or partial failures, so it's not fully transparent.

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 a single sentence plus two brief qualifiers (endpoint and tier). It is front-loaded with the main action and resource, and every phrase adds value without redundancy.

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 one-parameter tool, the description is reasonably complete: it covers the operation, the ID limit, the HTTP mapping, and a permission tier. It lacks a description of the return format (no output schema exists), but this is a gap given the promise of 'full subscription records'.

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 0%, but the description adds critical parameter meaning by stating the array contains 'subscription IDs' and is limited to 1000. This clarifies the purpose of the subscriptionIDs parameter beyond the raw schema, although it could specify whether IDs must be unique or how overflow is handled.

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 specifies a clear action and resource: 'Get full subscription records' for up to 1000 subscription IDs. This distinguishes it from siblings like search_subscriptions (which implies searching) by emphasizing retrieval by IDs. The explicit endpoint mapping further clarifies its function.

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 context is implied: use when you have subscription IDs to fetch. However, it does not explicitly state when to use this tool instead of alternatives like search_subscriptions, nor does it mention exclusions or prerequisites. The endpoint mapping provides some context but no clear guidance.

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