agenta_subscriptions_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: no pagination behavior, no auth requirements, no return shape, no statement of what a 'subscription' contains. Two words cannot cover a read operation's behavior.

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?

It is a single short phrase with zero waste and is front-loaded, but its brevity stems from under-specification rather than disciplined editing. There is nothing to restructure, and nothing to trim either.

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?

With no annotations, no output schema, and no description of the returned subscription records or pagination, the definition is not complete enough for an agent to know what it will receive. The only adequately documented element is the limit parameter, covered by the schema.

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?

There is a single parameter (limit) with 100% schema description coverage, including default and min/max bounds, so the schema already does the work. The description adds no additional meaning, which matches the baseline 3 for high-coverage schemas.

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 gives a verb and resource ("List subscriptions"), so the agent knows the operation type, but it is essentially a restatement of the tool name and says nothing about scope (whose subscriptions, any filters, account-level vs. plan-level). It does not differentiate from siblings like agenta_subscriptions_cancel or agenta_subscriptions_change_plan beyond the obvious verb.

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?

There is no guidance on when to use this versus the other subscription or list tools (agenta_customers_list, agenta_invoices_list, etc.), nor any prerequisites. The agent must infer everything from the name alone.

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