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

Annotations already declare read-only, idempotent, and open-world hints, and the description adds useful context: it returns attribute rows and geometry, and gives a quick sampling strategy. It doesn't discuss rate limits or performance implications of requesting geometry, but given annotation coverage, this is a solid score.

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 entire description is two sentences: the first clearly states purpose and key parameters, the second provides a practical tip. No wasted words, and the most important information is front-loaded.

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 query tool with six parameters and no output schema, the description effectively explains the return format, the source of the URL, and a quick-start approach. It doesn't mention pagination limits beyond what the schema already documents, and the absence of an output schema is partially compensated by the 'Returns attribute rows (and geometry)' statement. Overall, it's quite complete but misses minor behavioral details like error handling.

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 100%, so parameters are fully documented. The description reinforces the 'SQL-like where' and 'comma-separated out_fields' but adds little beyond the schema. The sampling tip is helpful for parameter usage but doesn't significantly elevate semantics beyond the baseline for high coverage.

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, with a specific verb and resource. It also implies the output (attribute rows and geometry) and references search_datasets as the source, distinguishing it from siblings like layer_info and search_within.

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 indicates the intended workflow by specifying the URL comes from search_datasets, and it provides a concrete sampling tip (where='1=1' + out_fields='*'). However, it doesn't explicitly name alternative tools or state when not to use this tool, 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.