set_global_script_dirs

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

Indicates it sets (mutates) directories, which is clear, but does not specify whether it replaces or appends, persistence, or required permissions. With no annotations, more detail is needed.

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?

Short and to the point, but the Args line is redundant with the schema. Could be more concise by omitting the Args section.

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?

Adequate for a simple mutation with one parameter and no output schema, but misses details on how directories are set (overwrite vs append) and impact on execution.

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?

Repeats schema information ('List of directory paths') without adding semantic meaning like accepted formats or constraints beyond the type.

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?

Clearly states it sets global script directories for Squish test execution, distinguishing from sibling 'get_global_script_dirs' which retrieves.

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?

No explicit guidance on when to use versus alternatives. The name implies configuration setting, but lacks context like when to set vs get or prerequisites.

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