ls

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

The description provides minimal behavioral information: it lists files. It does not disclose whether the operation is safe, what happens with invalid paths, or the output format. With no annotations, this leaves the agent with little insight beyond the basic action.

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 very short and front-loaded, but its brevity sacrifices completeness. Important details (like the path parameter) are omitted, making it less helpful than it could be.

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?

Given the existence of an output schema (not shown) and the simplicity of the tool, the description is still too sparse. It does not explain the tool's behavior under different conditions, error handling, or how to use the path parameter effectively.

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 for the 'path' parameter, and the description does not mention it at all. The description fails to add meaning beyond the schema, leaving the agent unaware of the parameter's usage.

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 'Lists files in the current directory', which clearly conveys the action and resource. However, it does not account for the optional 'path' parameter that allows listing a different directory, so it is slightly incomplete.

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 guidance on when to use this tool versus its siblings (e.g., list_objects, cd, pwd). The description does not provide context for choosing ls over alternative listing or navigation commands.

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