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

Annotations already declare readOnlyHint and idempotentHint, so the bar is lower. The description adds 'Returns attribute rows (and geometry)' and 'SQL-like where', which provide useful behavioral context beyond the annotations, but does not detail error handling or rate limits.

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: the first states purpose and key parameters, the second provides a concrete usage tip. No extraneous information, clearly 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?

Although there is no output schema, the description mentions the return type (attribute rows and geometry). Parameter descriptions are complete, and examples illustrate typical use. Missing details on pagination with offset, but the coverage is good for a query 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 description coverage is 100%, so baseline is 3. The description adds value by showing typical usage patterns (e.g., 'where="1=1"', 'out_fields="*"') and explaining the SQL-like syntax, which enhances understanding beyond the schema's parameter descriptions.

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 'Query an ArcGIS Feature Service / Map Service layer by its url', specifying a precise verb and resource. It distinguishes from siblings by referencing 'from search_datasets', indicating the source of the URL, and the context signals show it is separate from dataset discovery tools.

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 provides explicit usage guidance with 'Use where="1=1" + out_fields="*" to sample.' It implies the tool should be used after searching datasets, but does not explicitly state when not to use it or compare to alternatives like layer_info.

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