state_gis_services

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

The annotation readOnlyHint=true already declares the tool's read-only nature. The description adds context about querying the state's ArcGIS REST endpoint and listing folders/layers, but does not disclose potential latency, pagination, authentication requirements, or output format. No contradiction exists between description and annotations.

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 three short, purposeful sentences. The first sentence fronts the main action, the second adds precision about the resource, and the third provides usage context. No redundant or filler content.

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?

No output schema exists, but the description explains what the tool lists and how to use the results for state_gis_query. It does not specify the exact return structure or whether nested folders are included, but for a discovery tool with strong annotations and schema, this is adequate.

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 coverage is 100% and both parameters are well-documented: state has a full enum of state codes, folder has an example. The description does not add additional meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 specific verbs 'Discover' and 'Lists' with a clear resource: 'GIS services' / 'service folders and layers' on the state's ArcGIS REST endpoint. It also distinguishes itself from sibling tools by explicitly referencing state_gis_query as the downstream consumer of the results.

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 gives clear context by stating 'Use the results to find service paths for state_gis_query', which positions this tool as a prerequisite discovery step. It does not explicitly mention alternatives or when not to use it, but the guidance is sufficient for an agent to understand the typical invocation flow.

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