Listar Proyectos

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

With no annotations, the description carries the behavioral burdenasi. 'Lista los proyectos .starc disponibles en el directorio configurado' clearly communicates a read-only listing over the configured directory filtered to .starc projects. It does not mention edge cases or side effects, but the verb and file-type restriction transparently convey the operation.

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?

One concise, front-loaded sentence; every phrase adds relevant scope (list operation, .starc file type, configured directory).

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 zero-parameter listing tool with an output schema, it covers the essential operation and scope. It could mention whether the list is sorted or limited, and it doesn't differentiate from info_proyecto, but these are minor for invoking correctly.

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?

There are zero parameters, so the schema is trivially complete. The description clarifies that 'directorio configurado' is a fixed environment context rather than an input, which avoids inventing a path parameter.

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 uses a specific verb and resource: 'Lista los proyectos .starc disponibles en el directorio configurado.' It clearly states the operation (list), the object (.starc projects), and the scope (configured directory). It also distinguishes itself from sibling tools like listar_snapshots or info_proyecto by naming the exact file type.

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 is given about when to use this tool versus alternatives such as info_proyecto or leer_guion. The description implies a simple listing action, but it does not state what an agent should do with the results or when another tool would be a better choice.

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