features_select_by_location

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

No annotations provided, so description carries full burden. It discloses that the tool selects features and mentions mode (set/add/intersect/remove) but does not explain these modes or side effects on existing selection. Lacks details on prerequisites like layer existence or visibility.

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?

Two sentences, no fluff, front-loaded with core action. Every sentence adds value.

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 moderately complex tool with 4 parameters, no output schema expected, description is minimal. Missing context like selection modification behavior, expected layer properties, and mode semantics. Adequate but not comprehensive.

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 has 0% description coverage, so description must compensate. It explains predicate values and references mode from another tool, but does not define mode behavior or default, nor explain reference_layer_id. Adds some meaning but incomplete.

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 clearly states it selects features on a specific layer based on spatial relationship to another layer, listing predicate options. It distinguishes itself from siblings like features_select_by_expression (which uses expressions) and features_select_by_rectangle (uses a rectangle).

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?

The description implies its use for spatial selection against another layer but does not explicitly state when to choose it over alternatives like features_select_by_rectangle or features_select_by_expression. No exclusions or context provided.

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