codebase_watch

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

With no annotations, description covers initial incremental update and debounced watching. However, it does not disclose potential resource consumption, limitations, or side effects of stopping. Adequate but not rich.

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?

Two sentences, no redundancy. All information is essential and front-loaded. Efficiently conveys core behavior.

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, but description does not explain return values for 'status' action or confirm behavior on stop. Given complexity, it could be more complete about operational details.

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% (both parameters described). The description does not add new meaning beyond the schema's property descriptions, so baseline 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?

Clear verb 'Start/stop watching' and resource 'project directory for file changes and automatically update the index'. The description differentiates from siblings like codebase_update by specifying continuous watching behavior.

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?

Implies usage for continuous indexing but lacks explicit guidance on when to use this tool versus alternatives like codebase_update (manual update) or codebase_status (snapshot). No when-not-to-use or context for stopping.

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