list_subscriptions

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

No annotations are provided, so the description carries the full burden. It indicates the tool lists active subscriptions with counts, implying a read operation, but does not explicitly confirm it is read-only or mention authentication or side effects. Adequate but could be more 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 with three sample prompts, making it concise and front-loaded. Every element serves a purpose, and the structure is efficient for AI consumption.

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?

Given the tool's simplicity (no parameters, has output schema), the description is complete. It specifies the scope ('active feed subscriptions' with counts) and provides usage prompts, adequately informing an AI agent.

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 are no parameters, and schema coverage is 100%. Per the guidelines, the baseline is 4. The description does not need to add parameter information, and it appropriately provides context about what the tool returns.

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 lists active feed subscriptions with item counts, specifying the verb (list) and resource (subscriptions). This distinguishes it from siblings like subscribe, unsubscribe, and get_feed_items.

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 includes sample prompts that illustrate when to use the tool, such as 'Show my subscriptions' and 'What feeds am I following?'. However, it does not explicitly state when not to use it or list alternatives, which could be improved.

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