addWatcher

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Add watcher'. It does not mention that this is a write operation, whether it requires specific permissions, what side effects occur, or what the response looks like. The agent has no information about the tool's behavior beyond the inferred action.

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 short at two words, but this is under-specification rather than conciseness. It does not contain enough information to be useful. While there is no wasted verbiage, the description fails to convey even the fundamental purpose or scope of the tool.

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 lack of annotations, output schema, and any descriptive text, the tool is entirely contextless. The presence of nested path and body parameters with required fields suggests a non-trivial operation, but the description provides no explanation of how the parameters relate or what the tool accomplishes. It is completely inadequate for an agent to use correctly.

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 0%, so the description must compensate by explaining the parameters. It does not mention `user_id`, `issueId`, or `format` at all. The nested structure and required fields are only visible in the schema, and the description provides no additional meaning or context for these parameters.

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 'Add watcher' restates the tool name in plain language but does not specify what resource the watcher is added to or what 'watcher' means in this context. It could be adding a user as a watcher to an issue, a project, or something else, so it lacks the specificity needed to distinguish it from sibling tools like addUserToGroup.

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 is provided on when to use this tool versus alternatives such as removeWatcher or other user-related operations. There is no mention of prerequisites, typical scenarios, or why an agent would choose this tool over similar ones.

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