ls

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

With no annotations, the description carries the full burden. It does disclose return content (names, inodes, sizes, MAC times, deleted flags, alternate data streams), which is useful behavioral context, but it does not state read-only safety, image/part requirements, pagination or limit behavior, or side effects.

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 front-loaded sentence that immediately states the action and then enumerates the key output fields. There is no wasted wording or redundant framing.

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 five-parameter forensic listing tool with no annotations, no output schema, and 0% schema description coverage, the description is materially incomplete. It explains some output attributes but leaves required parameters, optional parameters, limit behavior, and safety expectations undocumented.

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%, so the description must compensate for five undocumented parameters. It partially clarifies the path parameter with the 'path or inode:N' syntax, but image, part, limit, and show_deleted are not explained at all.

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 states a specific verb and resource: 'List a directory,' and adds the path/inode input syntax plus the listed attributes. It clearly distinguishes this as directory enumeration rather than file reading, extraction, or single-file stat, but it does not explicitly name or route to sibling 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?

It gives only implied usage by saying it lists a directory and accepts a path or 'inode:N'. There is no explicit when-to-use guidance versus alternatives like find, stat, read, or extract, and no stated preconditions or exclusions.

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