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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds the return format (attribute rows and geometry) and query characteristics (SQL-like where, sampling pattern), which goes beyond the annotations and helps the agent predict behavior.

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?

Two sentences, front-loaded with the core purpose, including key parameters and a usage tip. Every word earns its place, and the backticked parameter names improve readability.

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?

Given no output schema, the description explains that it returns attribute rows and geometry, which is essential. It also ties into the search_datasets workflow and gives a sampling pattern. It does not cover edge cases (e.g., pagination limits) but the schema covers those, and the tool is relatively simple.

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?

The input schema already has 100% coverage with descriptions for all six parameters, so the baseline is 3. The description summarizes parameter types (SQL-like where, comma-separated out_fields) but does not add significant meaning beyond the schema. The examples in the schema are more informative than the description text.

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, using a specific verb and resource. It also mentions the URL comes from search_datasets, which distinguishes it 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 gives a clear context: use with a URL from search_datasets, and provides a concrete sampling pattern (where="1=1" + out_fields="*"). However, it doesn't explicitly exclude alternatives or state when not to use it, though the reference to search_datasets implies a workflow.

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