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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context by specifying what the tool returns (name, summary, record_count, owner/org, url) and how the output should be used, going beyond the structured annotations without contradicting them.

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 purpose, and every clause earns its place. It is concise, yet packs in the scope, returns, and downstream usage without unnecessary verbiage.

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?

Despite lacking an output schema, the description fully covers the expected return fields and how to use the result (pass url to query_layer/layer_info). This is sufficient for a search tool, and the sibling context doesn't introduce missing requirements. Comprehensive enough for tool selection and invocation.

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 input schema already covers all three parameters with descriptions (coverage 100%), so the baseline is 3. The description does not add additional parameter-specific semantics, but the return-value explanation and workflow hint provide some context beyond the schema. No major gaps.

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 verb 'Search' with a specific resource ('Fairfax County GIS open geospatial datasets') and gives useful category examples. It also distinguishes itself from sibling tools by mentioning the chain to query_layer / layer_info, making its role in the tool ecosystem explicit.

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 the primary use case: finding datasets by keyword and then passing the returned URL to query_layer or layer_info. It does not explicitly list exclusions or alternative tools, but the chaining instruction provides clear context for when to use this tool.

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