List resource subscriptions

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint. The description goes beyond them by naming the underlying native GET /resource_subscriptions, the required authorization scope for resource types, and that no local effect approval is required. It still omits pagination/rate-limit behavior.

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 short and front-loads the core purpose before technical auth details. The sentences are dense but each adds some operational context; there is no filler.

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 two-parameter, read-only list tool with rich annotations and full schema descriptions, the definition is mostly complete: it covers auth scope and read-only behavior. It does not describe return format or pagination, but no output schema exists and none is required for correct invocation.

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%, so the enum values and account parameter are already documented. The description adds only a small amount of meaning by contrasting 'sale event' authorization with 'other events,' but it does not explain the optional account parameter or enum selection mechanics.

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+resource ('List resource subscriptions') so the agent can identify it as the read counterpart to create/delete_resource_subscription. It does not explicitly call out those siblings or differentiate conditions beyond the name.

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?

Implied usage is clear from the list verb, and the description adds authorization context: view_sales for sale events, provider authorization for other events. However, it does not state when to prefer this over siblings or any exclusions.

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