Watch List

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

No annotations are provided, so the description carries the full behavioral burden. It says the tool changes notification subscription state, but does not disclose idempotency, permission/auth requirements, whether existing subscriptions are replaced, the delivery channel for notifications, or what an unsubscribe destroys.

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?

A single sentence with the action and the purpose front-loaded, and zero filler. Nothing in it is redundant or misplaced.

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 toggle tool with full schema coverage and no output schema, the description is nearly sufficient — the resource, action, and effect are all present. It falls short only on behavioral detail (return value, permissions, notification mechanics) that a no-annotation tool ideally supplies.

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%, and both parameters (listId, subscribed) are already documented in the schema, including the true/false toggle meaning. The description adds no syntax, format, or edge-case detail beyond what the schema provides, 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?

The description states a specific verb pair (subscribe/unsubscribe) and resource (watching a list) plus the effect (activity notifications). It implicitly distinguishes itself from the sibling watch_card by naming the 'list' resource, though it never names the 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 implied by 'for activity notifications' — an agent can infer you call this when you want to be notified of list activity. However, there is no explicit when-to-use/when-not guidance, no mention of the watch_card alternative, and no prerequisites such as notification or permission requirements.

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