list_directory

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

With no annotations, the description carries full burden for behavioral disclosure. It only states it lists files, but omits critical behaviors: how it handles missing directories, whether it uses SSH, performance implications, or if it traverses recursively. The agent cannot predict side effects or constraints.

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 extremely concise (one sentence), but it sacrifices necessary detail. It would be better to expand slightly to cover key parameters and usage context, so the conciseness is not earned.

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 no output schema, 3 parameters with no descriptions, and no behavioral hints, the description is grossly incomplete. It fails to inform the agent about return values, error handling, or parameter effects, making it insufficient for correct invocation.

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 on parameters, and the description adds no explanation for 'alias', 'path', or 'long'. An agent has no understanding of what each parameter does or what values are acceptable beyond basic types and defaults.

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 clearly states the action ('list files') and the resource ('remote directory'), making the primary purpose understandable. However, it does not differentiate from sibling tools like 'read_file' or 'tail_log_file' that also involve file listing.

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 alternatives. The description does not mention prerequisites, failure scenarios, or under what conditions it is appropriate to call list_directory instead of other file-related tools.

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