obtener_netlist

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

With no annotations, the description carries the full burden. It discloses the return payload (DSS files plus content) but says nothing about side effects — whether it writes files to disk, where the 'directorio' default ('temp_export') is rooted, whether it overwrites, or what permissions are required.

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?

A single, front-loaded sentence with no filler; the action and result are stated immediately. It is efficient, though perhaps a touch terse for the tool's complexity.

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 tool with no annotations, no output schema, and an undocumented parameter, the description is too thin. It does not address side effects, output location, file format details, or failure modes that an agent would need to invoke it 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?

Schema description coverage is 0% and the single parameter 'directorio' is undocumented in both schema and description. The description does not explain what directory means, whether output is written there, or its relationship to the returned files.

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?

States a specific verb+resource ('Exporta el circuito') and specifies the return payload ('todos los archivos DSS y su contenido'). An agent understands what it produces, though it does not differentiate itself from nearby export/snapshot siblings such as exportar_snapshot_proyecto_p7a or construir_snapshot_proyecto_p7a.

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 indication of when to use this versus the many other export/snapshot/listing tools in the sibling set, and no prerequisites or context. The agent is left to infer usage entirely.

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