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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context by specifying exactly what information is returned (fields, geometry type, record count, capabilities), which goes beyond the annotations and helps the agent anticipate the tool's output.

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 action and resource, then lists specifics. Every phrase earns its place, with zero filler or repetition of annotations.

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 parameter, strong annotations, and no output schema, the description is complete. It defines the input (URL), the purpose (schema retrieval), and the expected return items (fields, geometry type, count, capabilities). No critical information is missing.

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%, and the single parameter 'url' is clearly documented as a Feature/Map Service layer URL. The tool description's mention of 'by url' adds no significant meaning beyond the schema. Baseline 3 applies because the schema already carries the semantic weight.

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 opens with a specific verb 'Get' and names the resource 'an ArcGIS Feature/Map Service layer's schema'. It enumerates the exact return items (fields, geometry type, record count, capabilities), making its purpose unambiguous and distinct from sibling tools like query_layer that likely retrieve features.

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 the use case: when you need schema information for an ArcGIS layer. It does not explicitly name alternatives or exclusions, but the phrase 'schema by url' sets a clear context. A brief note about using query_layer for data queries would strengthen this, but it is not required.

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