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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds detail about what is returned (fields, geometry type, record count, capabilities). However, it does not disclose any additional behavioral traits such as network dependence, potential latency, or error conditions. The description adds some value but does not go beyond the safety profile already covered by annotations.

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 a single, compact sentence that front-loads the verb and resource, then enumerates the specific outputs. No filler words or redundancy, every part contributes to understanding.

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 the tool's simplicity (one parameter), strong annotations, and a description that lists all key return components, the description is complete for an agent to understand what the tool does and when to use it. No output schema exists, but the description compensates by naming the schema fields, geometry type, record count, and capabilities.

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 has only one parameter (url) with a clear description and example, covering 100% of parameter semantics. The tool description merely restates 'by url' without adding any new meaning beyond the schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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 uses a specific verb ('Get') and clearly identifies the resource ('an ArcGIS Feature/Map Service layer's schema by url') with explicit output components (fields, geometry type, total record count, capabilities). This distinguishes it well from sibling tools like query_layer, which would be for data retrieval rather than schema introspection.

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 makes the tool's purpose clear—obtaining schema metadata for an ArcGIS layer—which implicitly guides when to use it (before querying or using layer data). It does not explicitly name alternatives or state when not to use it, but the context is sufficiently clear due to the tool's focused scope.

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