read_directory_script

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

No annotations are provided, so the description carries the full burden. It implies a safe read operation and discloses the search scope (scripts/ and drafts/) plus the intended read-before-mutate workflow, but says nothing about error behavior, whether the read has side effects, or how the 'sync' flag changes runtime behavior.

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?

Two sentences, front-loaded with the action and scope, with the Get-Content parallelization arriving as useful secondary context. Nothing is padded, though the second sentence could have used its space to explain the parameters instead.

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?

With an output schema present, return values need not be described, and the read target is clear. The remaining gap is the unexplained 'sync' parameter and absent annotation coverage, leaving the agent uncertain about side effects.

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 description coverage is 0% across three parameters, and the description explains none of them. The 'sync' boolean (default true) is the most consequential unknown and is left entirely unexplained, so the description does not compensate for the coverage gap.

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?

States a specific verb and resource ('Read a Lua script') and scopes it to an 'outside folder project's scripts/ or drafts/ folder', which separates it from the plain read_script sibling. The only weakness is that the distinction from read_script is described by location rather than named directly.

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 gives when to use it ('inspect user project scripts before editing, validating, or syncing') and frames it as a replacement for PowerShell Get-Content, which anchors it against a familiar alternative. It does not state when to prefer read_script or read_project instead of this tool.

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