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 the return value details but does not disclose potential behaviors like network requirements, authentication needs, or error handling. It doesn't contradict annotations but provides limited extra context beyond what annotations imply.

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 sentence that front-loads the action ('Get') and resource ('layer's schema'), then lists the exact output elements. Every word earns its place, with no filler or 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 there is no output schema, the description adequately enumerates the return values (fields, geometry type, record count, capabilities), which is sufficient for a schema lookup tool. It does not cover edge cases like authentication or invalid URLs, but for the tool's simplicity, this is reasonably complete.

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 schema has 100% coverage for the single 'url' parameter with a clear description and example. The tool description merely references 'by url' without adding new semantic details about URL format, validation, or accepted service types. With high schema coverage, the baseline score of 3 is appropriate; the description does not further compensate.

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 the tool gets an ArcGIS Feature/Map Service layer's schema by URL, listing the exact return items (fields, geometry type, record count, capabilities). This is a specific verb+resource pair that distinguishes it from sibling tools like query_layer, which likely queries data.

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 usage when you need schema information from a layer URL, which is clear context. However, it does not explicitly mention when not to use it or provide direct alternatives (e.g., query_layer for data), so there is no explicit exclusion but the intended use case is clear.

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