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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds that it returns schema details and record count, which is consistent and provides some context about the response content, but it does not disclose additional behavioral traits like potential latency or error conditions. With annotations handling safety, the description adds moderate value.

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, efficient sentence that front-loads the purpose and immediately lists the specific outputs. Every word earns its place; there is no filler or repetition.

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?

For a tool with one well-documented parameter, no output schema, and annotations covering safety, the description provides sufficient information: it states the input, the purpose, and the expected outputs. It does not cover potential edge cases or error handling, but these are not critical for a simple read-only schema lookup. The description is complete enough for an agent to use correctly.

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% for the single 'url' parameter, and the schema already explains it with an example. The description adds the phrase 'by url' which is redundant with the schema, and does not introduce new parameter semantics beyond what the schema provides. Baseline 3 is appropriate given 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 states a specific action ('Get'), a clear resource ('an ArcGIS Feature/Map Service layer's schema'), and enumerates the exact outputs (fields with name+type, geometry type, record count, capabilities). This unambiguously distinguishes it from siblings like query_layer, which would be used 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 clearly implies when to use it (when you need schema metadata for an ArcGIS layer) and the input is straightforward (the layer URL). However, it does not explicitly mention alternatives or when NOT to use it, such as pointing to query_layer for actual data. The context is clear enough that an agent would not confuse it, but explicit exclusions are absent.

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