select_all

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the operation without explaining any side effects, such as replacing the existing selection, applying to the specified image_id, or whether it is reversible. This is a significant gap for a state-changing tool.

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 short sentence with no wasted words, but it is under-specified. While it is efficient, it does not mention parameters or behavior, making it too terse to be fully useful. It earns its place as a basic purpose statement but lacks needed elaboration.

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?

Despite being a simple tool, the description is incomplete. It does not clarify how the selection is applied, any requirements (e.g., image must be open), or the impact on existing selection. An output schema exists but return values are not the issue; the missing operational context makes it inadequate.

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 the image_id parameter at all. The schema only provides the title 'Image Id' with no explanation of what it refers to or how it is used. The description fails to compensate for this lack of parameter context.

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 'Select the entire image' clearly states the tool's action (select) and target (the entire image). It distinguishes this from sibling selection tools like select_rectangle, select_ellipse, and select_layer_alpha by specifying 'entire image'.

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?

No guidance is given on when to use this tool vs alternatives. The description does not mention that this is the tool to use when the full image selection is needed, nor does it reference any sibling tools or exclude cases where other selection methods are more appropriate.

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