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 behavioral context by specifying the exact return fields (name, summary, record_count, owner/org, Feature Service url) and that it searches open geospatial datasets. This enriches understanding beyond annotations without contradiction.

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?

Two concise sentences front-load the action and resource, and every phrase adds value—from the dataset categories to the return fields and the explicit handoff to query_layer/layer_info. No wasted words.

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 tool is a straightforward search/discovery tool with no required parameters. The description covers what it returns, the scope, and the integration with sibling tools. Given the rich annotations and schema, no critical context is missing for an agent to select and invoke this tool correctly.

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%, with each parameter (limit, query, org_id) already described in the input schema. The description does not add parameter-level semantics beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb ('Search'), a precise resource ('Chester County GIS open geospatial datasets'), and lists categories ('parcels, addresses, zoning & public works'). It clearly distinguishes from siblings by naming 'query_layer' and 'layer_info' as downstream tools that consume the returned URL.

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 workflow: use this to discover datasets by keyword, then pass the returned Feature Service URL to query_layer or layer_info. This explicitly names the alternatives for querying data, giving clear guidance on when this tool is appropriate versus its siblings.

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