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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, covering the safety profile. The description adds behavioral context by specifying the exact return fields (name, summary, record_count, owner/org, Feature Service url) and the intended downstream usage, which goes beyond the 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 long, front-loaded with the action and scope, and includes essential details about return values and downstream usage. Every sentence earns its place with 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?

This is a simple, read-only search tool with only 3 well-documented parameters and rich annotations. The description provides the return fields and downstream tool guidance, making it complete for an agent to select and invoke the tool. An output schema is absent, but the description explicitly lists the return fields, which compensates.

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 has 100% description coverage for all parameters (query, limit, org_id), so the schema already documents them well. The description adds no additional parameter-level meaning beyond the schema; it only reiterates keyword search and the return payload.

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 searches City of Kinston GIS open geospatial datasets by keyword, which is a specific verb+resource+scope. It also distinguishes from siblings by explicitly mentioning the return of Feature Service URLs for 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 gives clear context: use this to discover datasets and obtain URLs for downstream tools. It names query_layer and layer_info as the tools to pass the returned URL to, which is strong usage guidance. However, it does not explicitly state when not to use this tool or mention alternatives for similar searches.

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