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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds useful behavioral context: it returns attribute rows and geometry, and supports SQL-like where clauses. It also discloses the parameterized nature of the query. No contradictions found.

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 two sentences, front-loaded with the core purpose, and lists key parameters in a compact, scannable way. The tip about sampling is practical and not redundant. Every sentence earns its place with no fluff.

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?

The description covers the main purpose, the return value (rows and geometry), and key parameter options. It does not explain default limit or pagination details, but those are in the schema. With no output schema, the return-type mention is valuable. It is complete enough for a straightforward query tool, though it could hint at error handling or access requirements.

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 all 6 parameters have descriptions in the input schema. The description reiterates some parameter usage (e.g., 'comma-separated out_fields') and adds a usage tip for sampling, but does not add significant meaning beyond what the schema already defines. This is the baseline for high schema 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 primary action: 'Query an ArcGIS Feature Service / Map Service layer by its url' – a specific verb and resource. It also ties the URL source to 'search_datasets', distinguishing it as a downstream step from dataset discovery and from sibling tools like layer_info or 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?

It explicitly mentions 'from search_datasets', implying a workflow: first find a dataset, then query it. It also gives a practical sampling tip with where='1=1' and out_fields='*'. However, it does not explicitly state when NOT to use the tool or name alternative tools for different query types (e.g., search_within for spatial filters).

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