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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds meaningful context by specifying the return payload (name, summary, record_count, owner/org, Feature Service URL) and the downstream use of the URL. It does not introduce contradictions and provides practical behavioral insight.

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 two sentences, front-loaded with the core action, and every word earns its place. It efficiently conveys scope, purpose, and follow-up steps without any fluff.

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 read-only search tool with optional parameters and rich schema, the description is complete. It covers what the tool returns, how to use the result, and the domain, making it self-sufficient even without an output 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%, so all parameters are already documented. The description adds value by explaining what happens with the returned URL (pass to query_layer/layer_info), but it does not add new semantics to the input parameters themselves, staying at baseline.

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 searches Fauquier County GIS open geospatial datasets by keyword, with a specific list of example datasets and the resource scope. It distinguishes itself by describing the return of a Feature Service URL to be used with query_layer/layer_info, differentiating it from those downstream tools.

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 for when to use this tool: to find datasets by keyword, and then pass the resulting URL to query_layer or layer_info. It does not explicitly mention when not to use it or alternative search tools, but the workflow is well implied.

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