Add watchers to a task

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

Without annotations, the description fails to disclose critical behavioral details such as whether adding watchers is idempotent, what happens on duplicate watchers, authentication requirements, or rate limits. It only states the HTTP method and tags.

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 extremely concise (22 words) but lacks structure. It combines the HTTP method, endpoint, action, tags, and body format in a single line. While not verbose, it sacrifices readability and completeness.

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?

Given the tool's complexity (nested parameters, no output schema, no annotations), the description is woefully incomplete. It does not explain input requirements, response format, error conditions, or usage context. A tool with two parameters requires more detail.

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?

The description does not explain the parameters at all. It mentions 'Body: application/json' but does not describe the `watchers` array format or the `task_id` path parameter. With 0% schema description coverage, the agent receives no guidance on parameter values.

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 explicitly states the action ('Add watchers to a task') and provides the HTTP endpoint, making the tool's purpose immediately clear. It distinguishes from siblings like 'remove_watchers_from_a_task'.

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 provides no guidance on when to use this tool, what prerequisites (e.g., task existence), or alternatives. The sibling list includes many related tools, but no comparison is given.

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