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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds the specific output elements (fields, geometry, count, capabilities) which is useful, but it does not disclose any additional behavioral nuances like error handling or potential URL requirements. With the annotations carrying the main safety disclosure, the description provides moderate added context.

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?

A single, well-structured sentence that front-loads the action ('Get') and the resource, then lists the specific payload elements. No filler or redundant text, making it highly efficient.

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 a single parameter and no output schema, the description effectively communicates what the tool returns (fields, geometry type, record count, capabilities). It gives an agent everything needed to decide whether to invoke it and what to expect in the response.

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 fully describes the only parameter 'url' with an example. Since schema_description_coverage is 100%, the description does not need to add more, and it merely mentions 'by url' without adding new meaning. Baseline 3 is appropriate.

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 it 'Get an ArcGIS Feature/Map Service layer's schema', specifying a precise verb and resource, and enumerates the returned items (fields with name and type, geometry type, record count, capabilities). This distinguishes it from siblings like query_layer which would focus on data retrieval.

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 implies the tool is for schema inspection rather than data querying, but it does not explicitly state when to use it relative to alternatives such as query_layer. There is no explicit 'when to use' or 'when not to use' guidance, so the usage context is only implied.

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