list_subscriptions

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It only mentions the data returned (status, plan), which is minimal; it fails to disclose crucial operational behaviors like rate limits, required permissions, or potential error states.

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, focused sentence. It uses no superfluous words, and the mention of the optional plan filter adds critical functional information concisely.

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 provides necessary context by suggesting real-world use cases ('reconciliation or an account page'). However, given the low schema coverage, it is incomplete as it does not explain the format of the expected output or the constraints on the input tokens beyond their existence.

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 very low schema coverage (25%), the description is helpful by clarifying the scope of the optional 'planId,' specifically mentioning the option 'optionally for one plan.' This adds semantic value to an otherwise generic optional string parameter.

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 the tool's purpose is to list subscriptions and specifies what data is returned (status, plan). By naming the resource and the action (List), it is easily distinguishable from sibling tools that perform 'create' or 'add' actions.

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 tool provides concrete use cases, such as 'reconciliation or an account page,' which implies usage scenarios. However, it does not explicitly state which alternative tools to use for modifying subscriptions, making the distinction between this tool and the siblings solely dependent on the verb 'List.'

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