Select Features

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

Annotations provide idempotentHint: true, which the description does not contradict. The description adds no extra behavioral context (e.g., whether selection is applied or toggled). With annotations present, the description is adequate but not enhanced.

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?

Single, clear sentence with no fluff. Efficient but could benefit from a second sentence about usage of the two parameters for better structure. Still, front-loaded and scannable.

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?

Given 3 parameters, no output schema, and sibling tools, the description covers the core function. However, it lacks specifics like the effect on existing selection, return value, or error conditions. It is minimally complete but leaves gaps.

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%, leaving the description to compensate. It mentions 'expression' and 'feature IDs', hinting at the two optional parameters, but fails to define the expression syntax, format of fids, or constraints like exclusivity. This is insufficient for zero-coverage parameters.

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 'Select features in a layer by expression or feature IDs', which is a specific verb+resource and clarifies the two selection methods. It clearly distinguishes from sibling tools like add_features, delete_features, or clear_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?

No guidance on when to use this tool versus alternatives like get_selection, clear_selection, or the difference between expression vs feature IDs. The description omits context about prerequisites or trade-offs, leaving the agent without decision support.

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