Add a line or cable to an OpenDSS distribution network model, specifying buses and length, and mark the workspace as modified.
Agrega una línea/cable y marca el workspace como MODIFICADO.
| Name | Required | Description | Default |
|---|---|---|---|
| bus1 | Yes | ||
| bus2 | Yes | ||
| fases | No | ||
| nombre | Yes | ||
| r1_ohm_km | No | ||
| x1_ohm_km | No | ||
| longitud_km | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses one important side effect—marking the workspace as MODIFICADO—but omits authentication requirements, error behavior, validation rules, and whether the operation is reversible.
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 a single front-loaded sentence with no wasted words. However, it is extremely terse for a tool with 7 parameters and no schema descriptions, making it undersized for the 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?
Given 7 parameters at 0% schema coverage, no annotations, and an output schema, the description should compensate by explaining parameter semantics and usage context. It does neither, leaving the agent without enough information to invoke the tool 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?
The schema has 7 parameters with 0% description coverage, and the description mentions none of them. It provides no meaning, format, units, or defaults for parameters such as bus1, bus2, longitud_km, fases, r1_ohm_km, or x1_ohm_km.
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 a specific verb and resource: añade una línea/cable. It is clear what the tool does, although it does not explicitly distinguish itself from sibling tools such as crear_circuito or agregar_transformador.
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?
There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only implied context is that it adds a line to the workspace.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.