list_subscriptions

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

With no annotations, the description carries the burden. It implies a read-only operation via 'List' and adds a valuable behavioral rule about never fabricating data on failure. However, it does not disclose pagination behavior, default fields returned, or relation expansion semantics beyond what the schema already exposes.

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?

Two short sentences with no fluff. The core action and filters come first, followed by an important safety warning. Every word earns its place.

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 tells the agent what the tool lists and how to filter, and it warns against fabrication. Yet with no output schema and no annotations, it omits the result shape, pagination details, and handling of empty results, leaving meaningful gaps for a 10-parameter tool.

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?

The schema covers 100% of parameters with descriptions, so a baseline of 3 applies. The description merely restates some key filters (client, plan, subcategory, date, active status) in human terms and adds no meaning beyond the schema's own parameter 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 ('List'), a clear resource ('subscription services'), and gives a concrete example (SS Seguridad alarm monitoring). The filter list further narrows scope)Skip This is distinct from siblings like get_subscription or list_subscription_catalog because it names the exact resource type.

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 lists available filters but gives no guidance on when to choose this tool over siblings such as get_subscription or list_subscription_catalog. There is no explicit 'use when...' or 'use alternative when...' information.

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