List subscription groups

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the context that returned IDs are intended for use with specific sibling tools, but does not disclose additional behavioral traits like pagination or error handling. Since annotations carry the safety profile, a 3 is appropriate.

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 short sentences with no unnecessary content. It is front-loaded with the primary action and immediately provides actionable follow-up instructions. Every sentence earns 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?

Given the tool's simplicity (3 params, 1 required), good annotations, and no output schema, the description is sufficiently complete. It clarifies the purpose and gives next steps, but could have mentioned filtering capabilities; however, the schema covers that. Overall, it is adequate for a list 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?

Schema description coverage is 100%, with each parameter described adequately (appId, limit, filter.referenceName). The description itself adds no parameter-specific meaning beyond what the schema already provides, so the baseline of 3 is correct.

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 function with a specific verb and resource: 'List subscription groups for an app.' It also distinguishes itself from siblings by mentioning how the returned group IDs are used with list-subscription-group-subscriptions or create-subscription, which adds purpose clarity.

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 gives explicit context for use: it lists subscription groups for an app and directs the user to follow up with returned IDs in other tools. It does not explicitly exclude alternatives, but the 'for an app' scope and next-step guidance imply appropriate usage.

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