siril_set_selection

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Set', which implies mutation, but does not state that the current selection is replaced, whether it requires a loaded image, whether it affects image data, or how errors are reported.

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, front-loaded sentence with no redundant wording. Every word contributes to identifying the action, the target, and the parameter semantics.

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 state-changing tool with no annotations and no parameter descriptions, the definition is quite thin. It omits coordinate units/origin, prerequisites, and behavioral effects. The presence of an output schema reduces the need to describe return values, but the remaining context is insufficient for confident correct use.

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?

The description adds meaning by mapping the terse parameter names w and h to 'width' and 'height' and by presenting the expected order as (x, y, width, height). However, with 0% schema description coverage, it still leaves gaps such as units, coordinate origin, bounds, and valid ranges.

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 ('Set') and a specific resource ('Siril image selection rectangle'), and it explicitly identifies the tuple as (x, y, width, height). This clearly distinguishes it from sibling tools like siril_run_command, siril_get_preview, and siril_get_stats.

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?

There is no guidance on when to use this tool versus alternatives, and no prerequisites or exclusions are given. The intended use is only implied by the name and description, with no mention of required prior state such as an image being loaded.

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