Run AutoCAD Command

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

The description discloses that improper formatting can cause deadlock, and notes the COM backend limitation. This adds significant risk awareness beyond the readOnlyHint annotation.

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 concise yet comprehensive, structured with a one-sentence purpose, a formatting example, and a highlighted warning. No redundant information.

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?

While the description covers input formatting and risks well, it does not explain the output or return value, and it omits prerequisites like requiring an open drawing. Given the complexity of running arbitrary commands, this leaves some gaps.

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 input schema provides a basic description and examples for the 'command' parameter. The tool description adds critical details about newline handling and the need for extra blank lines for menu-based commands, which are not covered in the schema.

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 explicitly states the verb 'Execute' and the resource 'an AutoCAD command string', with immediate clarification of the COM backend. This clearly differentiates from sibling tools which are specific named operations.

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?

The description provides explicit formatting instructions, examples, and a crucial warning about commands that finish at an option menu needing an extra blank line to avoid deadlock. However, it does not explicitly state when to choose this tool over the many specific sibling tools.

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