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

Annotations already cover read-only/idempotent traits, so the bar is lower. The description adds useful context beyond annotations by stating the return type (attribute rows and geometry) and providing a sampling pattern. It does not discuss pagination behavior, error cases, or performance implications, but this is not critical given the safety annotations.

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?

The description is three sentences, front-loaded with the core purpose, and every sentence contributes useful information (what it does, key options, sampling tip). No wasted words or redundancy.

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 tool with 6 parameters, good annotations, and no output schema, the description is sufficiently complete. It covers purpose, input source, return format, and parameter usage. It doesn't explain pagination/offset mechanics in depth, but the schema covers those. It could mention error handling or limits, but these are absent from the schema and not critical for basic use.

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%, so the baseline is 3. The description summarizes the parameters (SQL-like where, comma-separated out_fields, etc.) but does not add significant new meaning beyond the schema's own descriptions. The only slight addition is 'from search_datasets' indicating the URL source, but the schema already specifies the URL format. Therefore, the description adds minimal value over the 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?

The description clearly states the tool queries an ArcGIS Feature/Map Service layer by URL, which is a specific verb+resource. It distinguishes itself from siblings like search_datasets (which finds datasets) and layer_info (which likely describes layers) by focusing on data retrieval. The mention of returning attribute rows and geometry clarifies the output.

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?

It provides clear context: use this when you have a layer URL from search_datasets and want to retrieve data. It gives a practical sampling tip (where=1=1, out_fields="*") which implies when to use it. However, it doesn't explicitly state when not to use it or compare with alternatives such as layer_info or search_within, so it falls short of a 5.

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