addWatcher

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

No annotations are provided, and the description does not disclose behavioral traits. It is unclear whether the tool is destructive, requires authentication, or has side effects. The description carries the full burden for transparency but fails entirely.

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 at two words, but this is under-specification rather than effective conciseness. It omits critical information and does not front-load a clear purpose. Every word must earn its place, but here the two words do not provide enough value.

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 complexity of the input schema (nested objects with required fields) and the lack of an output schema, the description is highly incomplete. It fails to explain what the tool does, what parameters are for, or what the result looks like. The agent receives almost no actionable context.

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%, meaning no parameter descriptions exist in the schema. The description 'Add watcher' adds no meaning to the two parameters (pathParams and bodyParams) or their nested fields (format, issueId, user_id). The agent cannot infer parameter semantics from either source.

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' is a vague verb+noun phrase. It does not specify what entity the watcher is added to (e.g., issue, project), nor does it differentiate from sibling tools like 'addUserToGroup' or 'removeWatcher'. The description lacks the specificity needed to distinguish its purpose.

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 versus alternatives. There is no mention of context, prerequisites, or relationship to sibling tools like 'removeWatcher' or 'addUserToGroup'. Agents receive no help in deciding when to invoke this tool.

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