sassy_list_dir

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

Beyond the readOnly/idempotent annotations, the description discloses important behavioral quirks: dotfiles and common directories are skipped below the top level, per-level entry caps apply, depth is clamped, and warnings name how many items were hidden. This is exactly the kind of non-obvious behavior an agent needs to anticipate.

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?

Three dense sentences with no filler. The most important information (read-only, listing behavior) is front-loaded, followed by non-obvious limits and sibling routing. Every clause earns its place.

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 two-parameter directory listing tool, the description covers ordering, recursion, hidden entries, caps, warnings, and usage guidance. The output schema already explains return shape, so no additional output documentation is needed. Nothing an agent needs to call this correctly is missing.

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 schema has 0% description coverage, but the description compensates well for `depth` by explaining recursion, default value, and clamping to 1-10. The `path` parameter is not explicitly described, but its meaning is strongly implied by 'directory entries' and 'directory tree', so the slight gap is minor.

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 opens with 'Read-only. Lists directory entries' and immediately specifies the exact resource and behavior: directory listing with [FILE]/[DIR] prefixes and sorted output. It clearly distinguishes itself from siblings by stating that metadata queries belong to sassy_file_info and content reads belong to sassy_read_file.

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?

It explicitly says 'Use it to explore a directory tree' and names the sibling tools for other needs, making the when-to-use and when-not-to-use boundary explicit. This is textbook-level routing guidance.

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