latexmk_watch_stop

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

No annotations are provided, so the description shoulders the burden of disclosing behavior. It only states the action 'stop' without explaining side effects, error handling for invalid session IDs, idempotency, or what happens to the underlying process. This is insufficient for a mutating operation.

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 a single well-structured sentence, front-loaded with the verb and resource. Every word contributes meaning and there is no redundancy or filler.

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?

Given the tool's simplicity (one parameter, no output schema) and the absence of annotations, the description is minimally adequate but lacks important behavioral details such as whether the stop is blocking, what happens if the session does not exist, or whether it only affects the specific session. It is complete enough for a basic stop operation but not fully comprehensive.

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 input schema already provides full coverage of the session_id parameter, including its provenance from latexmk_watch_start. The description adds no further parameter context, so it meets the baseline for high schema coverage without adding extra semantics.

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 uses a specific verb ('Stop') and a concrete resource ('running latexmk watch session'), with a clear parameter ('session_id'). It fully distinguishes this tool from sibling operations like latexmk_watch_start and latexmk_watch_list.

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?

The description clearly implies when to use this tool: after launching a watch session with latexmk_watch_start. It provides clear context but does not explicitly mention alternatives or when not to use it, though the sibling names make that unnecessary.

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