Ase Select Rectangle

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says the selection is set to a rectangle. It does not disclose side effects like replacing the existing selection, coordinate clamping, behavior with zero-size rectangles, or whether any canvas pixel data is touched.

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 a single sentence with no filler, front-loading the verb and object. It is appropriately concise for a simple state-setting tool.

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?

For a low-complexity setter, this is largely usable, and output schema presence reduce the need to document return values. However, missing coordinate semantics and explicit selection-replacement behavior leave gaps an agent would need to handle safely.

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% and the description does not mention x, y, width, or height. The parameter names are self-explanatory as coordinates and dimensions, but the description adds no information about units, coordinate origin, bounds, or constraints.

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?

States a specific verb ('Set') and resource ('server-side selection') and specifies the shape ('rectangle'). This clearly distinguishes the tool from sibling selection tools like ase_select_ellipse, ase_select_all, ase_move_selection, and ase_get_selection.

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?

Usage is implied by the description and the shape keyword, but there is no explicit statement of when to choose this tool over ase_select_ellipse or ase_select_all. It does not discuss coordinate context, whether selection replaces an existing one, or any prerequisites.

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