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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat safety guarantees. It adds meaningful behavioral context by specifying the return shape and explicitly routing the url to downstream tools, going beyond the structured 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?

One focused sentence states the purpose, the scope, the returned data, and the downstream usage. Every clause earns its place, with no padding or repetition of schema details.

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?

The description names all key return fields even though there is no output schema, covering the main agent need. It also names the downstream tools, making the overall call flow clear. Minor gaps, like default org behavior, are already covered by the schema.

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 schema already documents query, limit, and org_id with examples and defaults. The description adds a small amount of context by framing the query as keyword search and specifying the output fields, but it does not materially expand parameter meaning beyond the schema.

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 a specific verb, 'Search', with a clear resource: 'City of Sumter GIS open geospatial datasets.' It also states the exact returned fieldstons, including the Feature Service url, which distinguishes it from sibling tools like query_layer and layer_info.

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 proper workflow: use this tool to discover datasets and then pass the returned url to query_layer or layer_info. It does not explicitly list when not to use it, but the search-and-query workflow is clear and distinct from sibling tools.

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