agregar_carga

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

No annotations are provided, so the description carries the full behavioral burden. 'Agrega' implies a mutation, but the description does not state side effects, validation requirements, whether the target bus must already exist, units, permissions, or whether the model is recalculated.

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 single sentence is front-loaded and free of filler, but it is too terse for an 8-parameter mutation tool. The structure is acceptable, but the content is under-specified rather than optimally concise.

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?

An output schema exists, so return values need not be explained. However, given 8 input parameters, no annotations, and 0% schema description coverage, the description is far too incomplete: it omits required parameter meaning, units, defaults, and preconditions for adding a load.

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 8 parameters with 0% description coverage, including required fields nombre, bus, and kw plus defaults for kv, kvar, fases, critica, and tipo_visual. The description only vaguely hints at symbol selection and does not document any parameter names, formats, units, or required usage.

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 and resource: 'Agrega una carga' and adds that it allows choosing the single-line diagram symbol. The purpose is clear, but it does not distinguish itself from nearby siblings such as agregar_linea, agregar_transformador, or configurar_tipo_carga_unifilar.

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?

Provides no when-to-use guidance, no prerequisites, and no alternatives or exclusions. The agent is left to infer that this tool should be used whenever a new load is needed on the single-line diagram.

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