select_layers

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

With no annotations, the description carries the full burden and discloses nothing about behavior: whether selection replaces or adds to the current selection, whether it changes the active layer, whether hidden/locked layers can be selected, or what happens on invalid UIDs.

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?

One short sentence with the key scope (in Painter, by UID) front-loaded and no filler. Its brevity is close to under-specification, but on the conciseness axis itself there is no waste.

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?

An output schema exists so return values need not be explained, but for a state-mutating selection tool with zero annotations and zero parameter documentation, the definition leaves the agent without the essentials needed to invoke it confidently.

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% for the single `uids` parameter. The phrase 'one or more layers ... by UID' only restates that it is a list of UIDs; it adds no detail on where UIDs come from, ordering, or handling of unknown IDs.

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 (select) and resource (layers) plus the mechanism (by UID) in Painter. It is distinguishable from the read-only siblings list_layers and find_layers, though it never explicitly contrasts itself with them.

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 indication of when to use this versus list_layers/find_layers, no prerequisites (e.g. that UIDs must first be discovered), and no statement of what selection accomplishes downstream. Usage must be entirely inferred from the name.

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