Run AutoCAD Command

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

Annotations only provide readOnlyHint: false, but the description adds critical behavioral context: COM backend only, the deadlock risk at option-menu prompts, the denylist being a guardrail not a security boundary, and the fact that ARX/LISP can extend available commands. This goes well beyond the minimal 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?

Even though the description is longer than average, every sentence earns its place. It flows from core purpose to usage examples to critical warnings to safety and alternative recommendations. It is front-loaded with the main purpose and structured in digestible paragraphs without waste.

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 the complexity of a raw command runner and the existing output schema (which covers return values), the description fully covers usage mechanics, edge cases, safety posture, and alternative tools. It is complete and self-sufficient for an agent to decide when and how to invoke it.

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 100% but only lists example commands. The description adds meaning to the 'command' parameter by explaining the newline convention, the extra-line requirement for prompt-terminated commands, and the denylist guardrail. This significantly enriches param understanding.

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 opens with a specific verb+resource statement: 'Execute an AutoCAD command string directly (COM backend only).' It clearly distinguishes this from the many typed sibling tools by framing it as the raw, low-level command interface. Sibling differentiation is explicit with 'Prefer the typed tools...'.

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 concrete usage instructions: append \n for Enter, use an extra blank line or '_X\n' to exit option menus and avoid deadlock. It also explicitly says when NOT to use it ('refuses obviously destructive commands') and names alternative typed tools that validate arguments. This is exemplary when-to-use versus alternatives guidance.

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