get_task_watchers

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. 'Get' implies a read operation, but the description doesn't clarify whether the watcher list includes current user, whether it requires any special permissions, what the return format is, or pagination behavior for large watcher sets.

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 sentence, efficiently conveying the purpose with zero wasted words. It's appropriately short for a tool with one simple parameter.

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 straightforward read tool with one parameter, the description is somewhat minimal. No output schema exists, so the return format (what a watcher object looks like) is undocumented. The description doesn't address whether the task must exist, error cases, or whether watchers differ from members. It's adequate for simple resolution but lacks depth for an agent needing robust 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 coverage is 100% and there's only one parameter (task_id) described as 'The task ID'. The description's word 'of a task' reinforces that task_id refers to the specific task whose watchers are returned, providing marginal added context. With a single param at full schema coverage, 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 'Get all watchers of a task' uses a clear verb+resource structure ('Get...watchers of a task'), which clearly states what the tool returns. It distinguishes from siblings like add_task_watcher/remove_task_watcher by focusing on retrieval, though it could be stronger by clarifying it's read-only versus get_task_members which also retrieves task-related members.

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 is provided. Nearby siblings get_task_members, get_task, get_tasks exist, but there's no note clarifying watchers vs assignees vs members. No prerequisites or exclusions are mentioned.

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