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 useful behavioral context by specifying exactly what is returned (name, summary, record_count, owner/org, Feature Service url) and how the result should be consumed. 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 two sentences, front-loads the core purpose, and includes a valuable downstream usage hint. Every phrase carries information; no filler or repetition of schema details.

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?

Even without an output schema, the description explicitly lists the return fields and explains how the result is meant to be used. Given the simple keyword-search nature and rich annotations, the description provides enough complete context for an agent to select and invoke the tool.

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%: query, limit, and org_id all have meaningful descriptions. The tool description itself adds no parameter-specific detail beyond 'by keyword', but the schema covers the parameters adequately, so the baseline 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 action ('Search East Baton Rouge GIS open geospatial datasets') and a clear resource scope ('parcels, addresses, public works & planning'). It distinguishes itself from siblings by defining its output as dataset metadata plus a Feature Service url for downstream use with query_layer/layer_info.

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 clear context: use this to discover datasets by keyword, then take the returned `url` to query_layer or layer_info. It does not explicitly state when not to use it compared to search_within or other siblings, but the downstream chaining makes the intended flow clear.

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