add_task_watcher

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description is purely performative ('Add a watcher to a task') with no explanation of side effects, whether permissions are needed, whether the watcher is notified, whether duplicate watchers are rejected, or what happens on failure. For a mutating tool with zero annotation coverage, this is a significant gap.

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?

Single short sentence, efficiently stated with no wasted words. However, the conciseness is achieved through under-specification rather than careful triage, and the tool name and description are near-duplicates of each other.

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 mutating two-parameter tool with no annotations and no output schema, the description should provide more context such as notification behavior, error conditions, or relationship to remove_task_watcher. The minimal one-line description is inadequate for the tool's complexity and leaves the agent without behavioral guidance.

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 the schema already documents both parameters (task_id as 'The task ID' and watcher_id as 'User ID to add as watcher'). The description adds no additional meaning beyond what the schema 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 states 'Add a watcher to a task' with a specific verb and resource. It is clear about the action but does not distinguish from siblings like remove_task_watcher or add_tag_to_task, though the resource and action are distinct enough that confusion is unlikely. It's functional but minimal.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites (whether the task must exist, whether the user must be a workspace member), no exclusions, and no indication of how this differs from add_tag_to_task or other add operations.

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