listar_directorio

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

No annotations provided. The description does not disclose behavioral traits such as permissions required, hidden file handling, recursion, or error cases. It only states the basic function, leaving the agent without important context.

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 concise with two sentences and an Args block, but lacks structure. It is front-loaded with purpose but incomplete; every sentence could be more informative. It is not overly verbose, but missing critical details.

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 tool's simplicity and existence of an output schema, the description remains incomplete. It does not specify whether listing is recursive, how dotfiles are treated, or what the output format includes. The output schema may fill some gaps, but behavioral context is lacking.

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%. The parameter 'ruta' is described only as 'ruta del directorio a listar', which merely restates the parameter name. This adds minimal value beyond the schema; the description fails to clarify format, allowed values, or default behavior.

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 tool lists files and subdirectories of a folder, with a specific verb 'Lista' and resource 'archivos y subdirectorios de una carpeta'. It distinguishes itself from sibling tools which are unrelated (e.g., network, security, encoding).

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 vs alternatives. There is no mention of prerequisites, exclusions, or context. The description only explains the parameter 'ruta' without providing usage direction.

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