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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the tool's safety profile is known. The description adds useful behavioral context by listing the return fields (name, summary, record_count, owner/org, url) and the intended downstream action, going beyond what annotations provide.

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: the first states the action and scope, the second states the return fields and the follow-up action. Every word earns its place, and the critical workflow hint is front-loaded in the second sentence. No filler or repetition.

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?

For a search tool with no output schema, the description is remarkably complete. It names the input (keyword), output fields (name, summary, record_count, owner/org, url), and explicitly how to use the result (pass url to query_layer/layer_info). This makes the tool self-sufficient even without an output schema.

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?

Input schema covers all 3 parameters with descriptions (query, limit, org_id) at 100% coverage, so baseline is 3. The description adds minimal new parameter semantics—it only reinforces that searching is by keyword, which is already in the schema. No additional detail about parameter behavior is provided.

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?

Description clearly states it searches Charleston County GIS open geospatial datasets by keyword, gives examples (parcels, addresses, zoning), and differentiates itself from siblings by specifying the returned URL is for query_layer/layer_info. This is a specific verb+resource+scope with explicit sibling distinction.

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?

Explicitly tells the agent to pass the returned URL to query_layer/layer_info, establishing a workflow and implicitly indicating when to use this tool (discovery) versus alternatives (querying/inspecting). This provides clear when-to-use guidance and names alternative tools.

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