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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the agent knows it's a safe read. The description adds the specific data returned, which is useful, but it does not disclose further behavioral aspects like authentication requirements or rate limits, which the annotations do not cover.

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, front-loaded sentence that immediately states the verb 'Get' and the resource, followed by a compact list of returned items. Every word contributes value; there is no redundancy.

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 simplicity (one parameter, read-only, no output schema), the description explains the key return elements (fields, geometry type, record count, capabilities), which is adequate for an agent to understand what to expect. It does not describe the exact format or any limitations, but that is not critical for a straightforward schema fetch.

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%: the 'url' property has a clear description and example. The tool description adds no additional parameter semantics beyond confirming that the URL is the input. Baseline 3 is appropriate since the schema fully documents the parameter.

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 identifies the tool as retrieving an ArcGIS Feature/Map Service layer's schema via URL, specifying exactly what is returned (fields, geometry type, record count, capabilities). This distinguishes it from siblings like query_layer, which focuses on querying features rather than schema.

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 implicitly indicates this tool is for schema inspection by URL, which is clear context for when to use it. However, it does not explicitly name alternatives or state when not to use it, though the distinct purpose from sibling query_layer is implied.

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