features_select_by_rectangle

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

With no annotations, description carries full burden. Discloses spatial intersection behavior, bbox coordinate order, CRS fallback, and mode semantics. Lacks details on error handling or empty results, but sufficient for typical use.

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?

Three sentences, minimal waste. Front-loaded with core action. Parameter explanations follow logically. Every sentence earns its place.

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?

Output schema present, so return values not needed. Covers key parameters and semantics. Could mention valid bbox range or coordinate order constraints, but overall complete for a spatial selection tool.

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 coverage 0%, so description must compensate. Explains bbox format ([xmin,ymin,xmax,ymax]), crs default (layer CRS), and mode relationship to sibling tool. layer_id omitted but self-explanatory. Adds value beyond schema.

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?

Clearly states it selects features by bounding box intersection. Gives bbox format and references sibling tool features_select_by_expression for mode meaning. Distinguishes spatial selection from expression-based 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?

Explains bbox CRS default and mode options, hinting at alternatives. Explicitly ties mode to sibling tool for consistency. Does not explicitly say when to use this over features_select_by_location or features_select_by_expression, but provides enough context.

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