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

Annotations already declare readOnly/openWorld/idempotent/non-destructive. The description adds concrete return-value details (name, summary, record_count, owner/org, URL) and an explicit integration pattern with sibling tools, which provides transparency about what to expect beyond the structured fields. No contradictions with 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?

The description is exactly two sentences: the first delivers the core purpose and scope, the second covers output and downstream usage. Every word is informative, no redundancy or filler.

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 listing the return fields and providing integration guidance. Combined with strong annotations and full schema descriptions, it is largely complete for a search tool. Minor gaps remain (e.g., sort order, matching behavior), but these are not critical for 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 covers 100% of parameters with clear descriptions for query, limit, and org_id. The tool description mentions 'by keyword' which aligns with the query parameter but adds no additional parameter-level meaning. The baseline of 3 applies since schema description coverage is high.

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's verb (Search), resource (City of Lubbock GIS open geospatial datasets), and scope (parcels, zoning, public works & city services). It explicitly distinguishes itself from sibling tools by naming query_layer/layer_info as the next step after receiving the URL, clarifying its role as a discovery tool.

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 provides a clear usage context: use to find datasets, then pass the returned URL to query_layer/layer_info for further data access. It implies the tool is the entry point for exploring available geospatial data, though it does not explicitly mention when to avoid it or compare it to alternatives like search_within.

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