list_subscription_groups

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 safety profile is fully covered elsewhere. The description adds no behavioral context of its own — nothing about pagination, result ordering, or whether groups are returned with nested subscriptions, which matters given openWorldHint implies a live remote call.

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 with the scope qualifier front and center; nothing is wasted. It is arguably over-compressed rather than verbose, leaving the reader with no routing information.

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 one-parameter read tool with rich annotations, the description is technically sufficient to invoke correctly. With no output schema present, though, some indication of what is returned (group identifiers, names, nesting) would have closed the remaining gap.

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 single appId parameter is fully documented in the schema (100% coverage), so the schema carries the burden. The phrase "for an app" implicitly ties the call to appId but contributes no extra semantics such as format or validity of the ID.

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 subscription groups") plus a scope qualifier ("for an app"), so the operation is unambiguous. It does not, however, distinguish itself from nearby siblings such as list_subscriptions or list_subscription_offers, which an agent could reasonably confuse with it.

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 no when-to-use guidance, no exclusions, and no pointer to alternatives such as list_subscriptions for individual subscriptions versus groups. Usage is only implied by the phrase "for an app".

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