list_notification_subscriptions

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

Annotations already declare readOnlyHint and openWorldHint, so the read-only nature is covered. The description adds the 'opted in/out' context, but does not disclose additional behavioral traits like pagination, default ordering, or that it returns only opt-in/opt-out statuses. It adds marginal value beyond annotations.

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 a single, concise sentence that clearly conveys the tool's purpose without any redundant wording. It earns its place with the clarifying parenthetical about opt-in/out status.

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 read-only list tool with well-documented parameters and no output schema, the description is mostly sufficient. It could mention what the response contains (e.g., a list of subscription records) or how filters interact, but the core intent is clear and the schema covers the parameter details.

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 all three parameters (limit, user_sys_id, notification_sys_id) have their own descriptions. The tool description does not add any parameter-specific meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses a specific verb and resource ('List user subscriptions to notifications') and clarifies the field's meaning ('who has opted in/out'). This clearly distinguishes it from sibling tools like list_notifications, which lists notification definitions rather than user subscription states.

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 implies the tool is for viewing notification subscription states but does not explicitly state when to use it over alternatives or mention exclusions. There are no references to list_notifications or related tools, so usage context is only implicit.

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