autocad_attach

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

With no annotations, the description carries the full burden and discloses key behavior: it binds the server, activate defaults to true, later commands reject if the bound document is no longer active, and COM may not expose every same-version process. It does not describe error behavior on failed binding or what happens if already bound, but the core behavioral traits are covered.

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 front-loaded with the binding purpose and then adds only necessary detail about parameters, activation behavior, and COM limitations. Every sentence earns its place, and the structure flows logically from purpose to usage to caveats.

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 tool's complexity, no annotations, and no output schema, the description is largely complete: it covers purpose, parameter sourcing, activation semantics, a critical dependency (bound document must remain active), and a COM limitation. It stops short of explaining return values or failure modes, which would be helpful for a tool that establishes a binding.

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, and it does: it explains that windowHandle is a decimal string from status/list calls, that document is a name or full path, and that activate defaults to true and activates the selected document. All three parameters gain meaning beyond the schema's type information.

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 states a specific verb and resource: bind the MCP server to an AutoCAD application window/process and document. It distinguishes this binding action from activation by explaining that activate defaults to true and that false only establishes the binding without activating it. An agent can tell this apart from sibling tools like autocad_activate_document.

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 explains where to get windowHandle and document values (from status/list calls) and clarifies that omitting them selects the current target. It also describes the activate flag's effect, giving clear context for when to use each behavior. However, it does not explicitly name alternative tools or state when not to use this tool.

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