remove_work_package_watcher

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

Annotations provide idempotentHint=true and destructiveHint=true. The description adds value by explaining that the tool changes notification behavior without deleting the user or work package, clarifying the nature of the destructive hint. However, it does not mention idempotency or other behavioral details.

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 consists of two concise sentences with no wasted words. The core action is stated first, immediately followed by usage guidance. Perfectly front-loaded and efficient.

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?

With no output schema, the description should hint at the return value or success indication; it does not. The explanation of side effects is partial. For a simple removal tool, it covers essential preconditions but lacks completeness regarding outcomes.

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 coverage is 0%, so the description must compensate. It mentions 'workPackageId and userId' but does not describe each parameter's purpose or constraints beyond verification. The schema already provides types and minimum values, but the description adds no semantic depth, leaving meaning to be inferred from the tool name.

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 'Unsubscribe a user from one work package's watchers,' which is a specific verb ('unsubscribe') and resource ('work package's watchers'). It clearly distinguishes from siblings like 'add_work_package_watcher' and 'list_work_package_watchers.'

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 advises 'Use only after verifying workPackageId and userId,' providing explicit context for safe usage. It clarifies side effects (changes notification behavior, no deletion) but does not explicitly exclude alternatives or mention when not to use.

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