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

With no annotations provided, the description carries the full behavioral burden and does well: it explains statement separation, Enter handling, follow-up answer placement, selection methods (ALL or P), and that it returns 'the command log and any problems.' It does not explicitly state permission requirements, undo behavior, or whether changes are destructive, but for a command runner the execution semantics are unusually well disclosed.

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 definition is dense but front-loaded: purpose first, then syntax rules, examples, and specialized 3D context. Every section is relevant, though the long example strings and command lists could feel heavy. For a complex command-scripting tool, the length is justified and structured.

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?

The tool is complex, has no output schema, and has no annotations, so the description must do the heavy lifting. It covers syntax, behavior, return values, object selection, 3D points and commands, and points to cad_list_commands for command discovery. Nothing essential for correct invocation appears missing.

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 description coverage is 100%, so the baseline would be 3, but the description adds significant meaning for the commands parameter: separators, tokenization, Enter semantics, examples, 3D point syntax, and relevant command families. The select parameter is mostly documented in the schema, and the description only briefly ties it to pre-selection and P. The extra syntax detail for commands makes this above baseline.

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 and resource: 'Runs AutoCAD command-line input in the current drawing, exactly as typed in the app.' It clearly distinguishes this from generic script execution by tying it to AutoCAD command-line syntax and the current drawing context. An agent can immediately tell this tool executes typed CAD commands.

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 gives substantial usage context through syntax rules and examples, but it does not explicitly state when to prefer this tool over siblings like cad_execute_script or cad_batch_add_entities. The only alternative named is 'Use cad_list_commands to see every command,' which is about discovery rather than execution choice. Usage is implied rather than contrasted.

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