Start Watch

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

Minimal disclosure: annotations provide non-destructive, non-read-only info but the description does not add behavioral traits like background execution, resource impact, or the need to eventually call project.watch_stop.

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?

Very concise (8 words) but too brief for the tool's complexity. Front-loaded purpose, but omitted critical context.

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?

Incomplete for a tool with 4 parameters, no output schema, and related siblings. Lacks information on return value, watcher lifecycle, and parameter constraints.

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 50% and the description adds no parameter details. Undocumented parameters (path, exclude) remain unexplained; the description could clarify their meaning or defaults.

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 clearly states the verb 'Start' and the resource 'incremental file watcher' scoped to a specific repository. However, it does not differentiate from sibling tools like project.scan or project.watch_stop, which would improve clarity.

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 (e.g., one-time scan with project.scan) or prerequisites (e.g., repository existence). The agent is left to infer usage context.

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