Find Entities in Region

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

Annotations declare readOnlyHint=true, which aligns with the read-only nature of 'Find'. The description adds behavioral detail 'crossing selection' beyond the annotation, indicating it selects entities intersecting or fully inside the rectangle.

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 sentence, no superfluous content. Front-loads the key action and resource. Efficient use of words.

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 the tool is simple with 4 required parameters and an output schema exists, the description adequately covers input and behavior. However, it omits coordinate system context, which might be assumed but could be clarified.

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 is 100% with clear parameter descriptions (e.g., 'Region minimum X'). The description adds minimal extra meaning beyond the schema, only clarifying the rectangular region 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 uses specific verb 'Find' and resource 'entities within a rectangular region', clearly distinguishing from sibling selection tools like analysis_select_by_layer or analysis_select_by_type. The parenthetical 'crossing selection' further clarifies the selection mode.

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 explicit when-to-use or when-not-to-use guidance is provided. The description implies usage for rectangular region selection but does not contrast with alternative selection methods (e.g., layer-based or type-based selections) that appear among sibling tools.

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