list_subscriptions

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

The description adds critical behavioral context beyond the annotations: 'Stream D Phase 4: stdio cannot decrypt subscription/category/account names.' This reveals a transport-specific limitation that affects the returned data. Annotations are readOnlyHint, idempotentHint, destructiveHint, none of which contradict this added context.

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 two sentences long, with the first stating the purpose and the second providing essential usage guidance. Every word earns its place; no redundancies.

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 simple schema (one optional parameter) and no output schema, the description covers the key behavioral constraint (transport limitation) and purpose. It lacks parameter documentation, but the enum is clear. Annotations cover safety. Almost complete for this 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 has one optional parameter 'status' with an enum, but schema description coverage is 0%. The description does not mention the parameter or explain its effect. While the enum values are self-explanatory, the description adds no value beyond the schema, and with 0% schema coverage, it should compensate.

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 'List all subscriptions,' which is a specific verb+resource. It distinguishes from sibling tools like add_subscription, delete_subscription, and get_subscription_summary. The additional note about decryption limitations further clarifies the tool's purpose.

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 explicit guidance: 'use HTTP MCP or the web UI for this query' when decrypted names are needed. This tells the agent when to use an alternative. However, it does not explicitly state when NOT to use this tool, leaving some ambiguity.

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