Watch Status

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

Annotations already indicate readOnlyHint=true (safe, no side effects), but the description adds no further behavioral context—e.g., what the watcher state consists of (boolean, list?), or how to interpret the response. The description is merely a restatement of the title.

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?

Extremely brief (4 words) but under-specified, not concise. Concision without completeness is not helpful. The description should be expanded to include essential details.

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?

No output schema and no description of what the tool returns. For a status tool, the return value is critical. Also lacks parameter explanations, making the tool poorly documented overall.

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 sole parameter repository_id has no description in the input schema (0% coverage) and the tool description does not explain it. With one required parameter, failing to describe its meaning is a serious omission.

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 'Current watcher state for a repository' is a noun phrase that implies the tool returns state, but lacks a verb like 'Get' or 'Retrieve'. While it distinguishes from sibling actions (watch_start, watch_stop), it's vague about what the state includes.

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 like watch_start or watch_stop. The agent must infer its purpose from the name and description.

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