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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety and mutability are covered. The description adds value beyond them by disclosing the return shape ("Returns attribute rows (and geometry)") and a low-cost sampling strategy. It does not mention rate limits or max-result handling, keeping it short of a 5.

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?

Three sentences that are front-loaded with the core operation, followed by return behavior and a sampling tip. The parameter-summary sentence lightly duplicates the schema but reads as a quick orientation. Generally efficient with little waste.

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?

With no output schema, the description compensates by naming the return content (attribute rows and geometry). Combined with full schema coverage and annotations, an agent has what it needs to call the tool; only rate/pagination limits for large layers are left to the schema.

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 the baseline is 3. The description briefly restates the parameters (SQL-like where, comma-separated out_fields, order_by, limit, offset) but adds only marginal meaning beyond the already-documented schema, so it does not exceed baseline.

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 gives a specific verb+resource ("Query an ArcGIS Feature Service / Map Service layer") and routes the agent to the sibling that supplies the url (search_datasets). It clearly separates itself from search_datasets, but does not differentiate from the closely related layer_info sibling. An agent can identify the operation, though one adjacent alternative is left ambiguous.

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 states a concrete sampling recipe ("Use where=\"1=1\" + out_fields=\"*\" to sample") and notes the url comes from search_datasets. However, it gives no explicit when-to-use/when-not guidance versus layer_info or search_within. Usage is implied rather than framed as a decision rule.

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