cad_call

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

No annotations are provided, so the description carries full behavioral burden. It does not disclose that arbitrary native operations may mutate or destroy drawing state, what permissions or bridge state are required, what happens on an unknown/invalid tool name, or what the response looks like. For a wildcard dispatcher that can invoke any operation, this is a substantial gap.

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?

Two short sentences with zero filler, and the primary purpose is front-loaded ahead of the discovery pointer. Every clause earns its place.

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 a 2-param tool with a free-form nested `args` object, no annotations, and no output schema, the description covers the discovery path but omits how to construct valid `args` and how this relates to the dedicated sibling tools. Adequate to invoke blindly, not complete enough to invoke correctly with confidence.

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 0%, so the description must compensate. It does map both params meaningfully: 'by name' explains the `tool` string, and 'with a JSON argument object' explains `args`. But it says nothing about where to find each operation's expected argument shape, leaving the free-form nested `args` object entirely unconstrained.

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 uses a specific verb ('Call') plus resource ('any native AutoCAD operation by name'), making clear this is a generic dispatch/escape-hatch tool rather than one of the dedicated siblings like draw_line or open_drawing. It also points at the discovery mechanism (list_tools), which sharpens its identity. It stops short of explicitly stating how it relates to the wrapped convenience tools, but the core purpose is unambiguous.

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?

It gives one concrete piece of context: use list_tools to discover valid operation names. However, it never says when to prefer cad_call over the many equivalent dedicated siblings (draw_line, move_entity, save_active_drawing, etc.), which is the central routing decision for this tool. Usage is implied rather than specified.

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