start_watch

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

Discloses file movement to <folder>/../done/ and auto-transcription, but omits error handling, supported audio formats, persistence, or concurrency. Without annotations, description carries full burden but is incomplete.

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?

Three sentences, each essential: first states purpose, second explains workflow, third directs to companion tool. No wasted words.

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?

Covers main workflow (start, auto-transcribe, move, retrieve results). With output schema existing and simple input, description is nearly complete. Missing: how to stop (stop_watch) or configure transcription.

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% (description includes path format). Tool description adds context by referencing folder in use case but does not enrich meaning beyond schema. Baseline 3 applies.

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?

Description clearly states verb 'start watching' and resource 'folder for new audio files to auto-transcribe'. It distinguishes from siblings like transcribe_audio (single file) and get_watch_results (retrieval).

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?

Tells agent to call get_watch_results for retrieved transcriptions, but no explicit when-to-use vs alternatives (e.g., transcribe_audio) or when-not-to-use. Lacks prerequisites or exclusions.

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