read_directory_project

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

No annotations exist, so the description carries the full burden. It usefully discloses that the operation runs "without shell commands" and is a read-style inspection, but says nothing about permissions, side effects, or whether the returned lists can be large.

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 tight sentences with the primary action front-loaded and a supplemental context line. No filler, though the "Context:" line is somewhat redundant with the first sentence's intent.

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?

An output schema exists, so return values need not be explained. Purpose and usage timing are covered, and the sole parameter is at least hinted at; the definition is complete enough to invoke, with only minor gaps around path expectations.

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 single parameter has 0% schema description coverage, so the description must compensate. It implies the argument is a "user-provided folder path" and an "outside folder project," which loosely maps to the directory param, but adds no format, absolute-vs-relative, or validation detail.

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 (Inspect) and resource (outside folder project) and enumerates what it returns: metadata, prompt, bwconfig, and script file lists. This distinguishes it from the generic read_project/read_script siblings, though it does not explicitly name those alternatives.

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?

"Use before editing or syncing any user-provided folder path" gives a clear timing/context cue, and "replaces PowerShell directory scans" clarifies the workflow it belongs to. No explicit when-not or named alternative tool, so it falls short of a 5.

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