latexmk_watch_list

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

With no annotations provided, the description must convey behavioral traits. It states it lists active sessions, which implies a read-only operation, but it does not explicitly confirm that it has no side effects, requires no special permissions, or describe what happens to the sessions. The behavior is minimally transparent but lacks explicit safety or scope details.

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 sentence that directly states the tool's function without any filler. Every word is necessary and it is appropriately sized for a simple list operation.

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 tool with no output schema and no annotations, the description is somewhat sparse. It clarifies what it lists (all currently active latexmk watch sessions) but does not describe the format of the returned data or any additional behavior. Given the simplicity of the tool, it is minimally complete but could benefit from stating the return type or confirming it does not alter sessions.

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 is empty, so with zero parameters the description has nothing to add beyond the schema. Per the baseline for zero-parameter tools, a score of 4 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?

The description uses a specific verb 'list' and clearly identifies the resource 'currently active latexmk watch sessions'. It distinguishes from sibling tools like latexmk_watch_start and latexmk_watch_stop which perform different actions, making the purpose unambiguous.

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 implies usage when the user wants to view active watch sessions, but it does not explicitly state when to prefer this over alternative tools or provide any exclusion criteria. No context is given for when not to use it, though the simple read-only nature makes this less critical.

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