jambavan_watch

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

With no annotations provided, the description discloses key behavioral traits: that each file save triggers an incremental re-index of just that file. It does not mention destructive actions or auth needs, but the tool is a safe watcher.

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 concise, with only three sentences that front-load the main purpose, then detail actions and behavior. Every sentence earns its place without redundancy.

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?

For a simple control tool with one parameter and no output schema, the description covers purpose, usage, and behavioral transparency completely. It provides all necessary information for an agent to select and invoke 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 coverage is 100% with one enum parameter. The description adds value by explaining the effect of each action (start, stop, status) beyond the schema's simple enum description, providing context on when to use each.

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 tool controls a live file watcher that keeps the index in sync, listing the three actions (start, stop, status) and their effects. It distinguishes from sibling tools like jambavan_index by focusing on watcher control rather than initial indexing.

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?

Explicitly advises 'Use "start" after jambavan_index, then forget about it', providing clear context on when to use this tool. Implicitly advises not to use before indexing, and alternatives are implied by sibling tool names.

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