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

Annotations already declare the tool is read-only, idempotent, and non-destructive. The description adds useful behavioral context: it returns name, summary, record_count, owner/org, and a Feature Service URL, and clarifies the data scope (Berks County open GIS). No contradictions.

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 well-structured sentences: the first states the core purpose, the second details the return payload and the next logical action. Every sentence earns its place without fluff or redundancy.

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?

With no output schema, the description compensates by enumerating return fields (name, summary, record_count, owner/org, url) and suggesting how to use the url. It is complete enough for a straightforward search tool, though edge cases like empty results or pagination are not discussed.

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?

All three parameters (query, limit, org_id) have descriptions in the schema, giving 100% coverage. The description reinforces the 'keyword search' aspect of the query parameter but does not add meaning beyond the schema examples. Baseline 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 uses a specific verb ('Search'), names the resource ('Berks County GIS open geospatial datasets'), and scopes it by keyword. It also distinguishes itself from siblings by listing return fields and explicitly pointing to query_layer / layer_info as 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?

It clearly states when to use this tool (searching datasets by keyword) and gives concrete next-step guidance (pass the returned url to query_layer or layer_info). It lacks explicit 'when not to use' exclusions, but the context is strong enough to guide selection.

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