send_command

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

With no annotations, the description carries full burden and delivers: it discloses a security filter, that modifications require confirm=true, and that SendCommand is asynchronous ('confirma el envio, no el exito'). This is rich behavioral context beyond mere function.

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?

Three concise sentences in Spanish, front-loaded with purpose and followed by critical usage and behavioral notes. Every sentence adds value with no redundancy.

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 an escape hatch tool with a simple schema and an existing output schema (which likely covers return format), the description covers purpose, usage constraints, and behavioral nuance (async, security filter). It is complete and self-sufficient.

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 coverage is 0%, but the description compensates by explaining 'command' as accepting commands or AutoLISP, and 'confirm' as mandatory for drawing modifications. While it doesn't detail command string syntax, it covers the essential semantic difference.

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 'manda comandos o AutoLISP a la linea de comandos' (sends commands or AutoLISP to the command line) and uses 'Escotilla de escape' (escape hatch), distinguishing it from all specific drawing tools as a general-purpose command executor. The verb and resource are explicit.

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?

Explicitly says 'Usala solo para lo que no cubre ninguna tool' (use it only for what no other tool covers), providing direct when-to-use guidance. It also specifies the confirm=true requirement for drawing modifications, an important usage constraint.

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