Select by Window

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

Beyond the readOnlyHint annotation, the description discloses key behaviors: corners may be in any order, selection uses drawn position rather than stored coordinates, and zero-area boxes are refused instead of returning an empty list. These caveats materially affect how an agent interprets results and errors.

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?

Three short, focused sentences front-load the core purpose and then cover only high-value edge cases. Every sentence earns its place; there is no redundant restatement of the schema.

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?

With a fully documented input schema, an output schema, and a readOnly annotation, the description covers the remaining behavioral context an agent needs: corner ordering, coordinate-space semantics, and invalid-input handling. Nothing required for correct invocation is 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 schema already documents all parameters. The description adds value by clarifying that the four corner parameters can be supplied in any order and that selection is based on drawn position, which is not obvious from the schema alone.

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/resource: 'AutoCAD's ssget window/crossing selection' and the title 'Select by Window' make the scope unmistakable. This distinguishes it from sibling tools like selection_polygon and selection_filter by its rectangular window/crossing semantics.

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 implies use for rectangular window/crossing selection, and the corner-order note gives operational context. However, it never explicitly says when to prefer this over selection_polygon or selection_filter, leaving the routing decision to inference.

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