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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is well covered. The description adds useful context about return content (name, summary, record_count, owner/org, URL) and downstream tools, but does not disclose potential search behaviors like pattern matching or result limits beyond schema defaults.

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-loaded with the primary action and scope, and every clause provides value including the return format and downstream tool references. There is no redundancy or fluff.

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?

Despite lacking an output schema, the description explains exactly what the tool returns and how to proceed with the results, which is essential for an agent. It does not mention pagination, ordering, or potential edge cases in search behavior, but given the annotations and schema, the description is largely sufficient for effective use.

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 (query, limit, org_id) having a clear description. The description adds no new parameter-level semantics beyond indicating that 'keyword' maps to the query parameter; it simply reinforces the top-level purpose rather than enhancing parameter understanding.

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 it searches Indian River County GIS open geospatial datasets by keyword, with specific examples like parcels, addresses, and zoning. It also distinguishes itself from siblings by explicitly noting it returns Feature Service URLs intended for use with query_layer and 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 that this is a discovery tool for finding datasets and returning URLs for subsequent queries, which guides the agent on next steps. However, it lacks explicit exclusions or direct comparison to sibling search tools, so it doesn't fully cover when not to use it.

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