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

The description adds value beyond annotations by detailing the specific data returned (fields, geometry type, record count, capabilities). The annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the safety profile is covered. The description aligns with these annotations and provides additional output context, earning a 4.

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, well-structured sentence that front-loads the action and resource, lists the key outputs, and contains no redundant words. It is appropriately concise for a tool with one parameter.

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 tool's simplicity (one parameter), the absence of an output schema, and the rich annotations, the description is complete. It explicitly names the four types of information returned, leaving no major gaps for the agent to infer. The context is entirely sufficient.

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 single parameter 'url' is fully described in the schema with an example, achieving 100% schema coverage. The tool description mentions 'by url' but adds no additional meaning beyond what the schema already provides. Baseline of 3 is appropriate since the schema 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 uses the specific verb 'Get' with a clear resource ('ArcGIS Feature/Map Service layer's schema') and specifies the exact output components: fields, geometry type, record count, and capabilities. This clearly distinguishes it from siblings like query_layer, which would focus on retrieving data 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 makes it clear that the tool is used to retrieve schema information via URL, which implies when to use it. However, it does not explicitly mention alternatives or when not to use it, though the sibling tool 'query_layer' suggests a clear alternative for data queries. The context is clear but lacks explicit exclusions or alternative names.

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