list_subscriptions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the agent knows this is a safe, repeatable read. The description adds only the grouping scope; it says nothing about whether results are paginated, how large a response can be, or what fields are returned on a subscription, which is the remaining behavioral value it could have provided.

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?

One short sentence, front-loaded with the action and resource, with no filler. It is efficient, though its brevity leaves the behavioral gaps noted above rather than trading length for completeness.

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 single-parameter read tool with full annotation and schema coverage, the description is adequate to invoke correctly. It stops short of covering the things an agent would still want for a list endpoint: result size, pagination, and how subscriptions relate to groupId when the group is empty or unknown.

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% and the single groupId parameter is documented as 'The subscription group ID'. The description's phrase 'within a subscription group' merely restates that scope without adding format, ID source, or example values, 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?

States a specific verb and resource ('List subscriptions') plus a scoping constraint ('within a subscription group'). This clearly separates it from the sibling list_subscription_groups, which lists groups rather than the subscriptions inside one, though the description does not name that sibling explicitly.

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?

Usage is only implied: the required groupId makes it evident you must know which group to enumerate. There is no explicit when-to-use/when-not guidance, no mention of list_subscription_groups vs this tool, and no note about pagination or limits on results.

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