list-subscriptions

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

With no annotations, the description carries the full burden. It adds the quota cost of 1 unit per call and implies read-only operation. However, it does not disclose error conditions, auth requirements beyond 'authenticated user', or pagination behavior. The quota note is useful but not comprehensive.

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 no redundant information. It front-loads the core action and includes a meaningful quota detail, earning 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?

For a simple list tool with two optional params and no output schema, the description covers the essential purpose and quota cost. It does not describe return format, but the schema covers pagination, and the lack of an output schema lowers the burden. The description is adequate for this simple context.

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 100% (both pageToken and maxResults are described). The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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 the authenticated user's channel subscriptions, using a specific verb and resource. It distinguishes itself from siblings like 'list-channels' (channel info) and 'subscribe' (creating a subscription).

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 provides clear context (authenticated user's subscriptions) but does not explicitly state when to use it vs. alternatives or exclusion cases. The presence of 'subscribe' and 'unsubscribe' siblings makes the use case obvious, but explicit guidance is lacking.

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