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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context by stating that the tool returns metadata including a Feature Service URL intended for use with query_layer/layer_info, which establishes a clear workflow. This goes beyond the safety profile provided by 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: the first states the purpose and examples, the second enumerates return fields and the follow-up tool usage. It is concise, front-loaded, and every sentence adds value without redundancy.

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?

Given the simple search tool with full schema descriptions and rich annotations, the description adequately covers what the tool does, what it returns (name, summary, record_count, owner/org, Feature Service url), and how to integrate with sibling tools. No output schema exists, but the return fields are explicitly listed, making it complete.

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 already provides 100% coverage for all three parameters (query, limit, org_id) with clear descriptions. The description's mention of 'by keyword' aligns with the query parameter but adds no new meaning beyond the schema. Thus, 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 opens with a specific verb ('Search') targeting a defined resource ('City of Branson GIS open geospatial datasets') and includes concrete examples ('parcels, zoning, public works & city services'). It also differentiates itself from sibling tools by instructing the agent to pass the returned Feature Service URL to 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 usage context: search datasets by keyword for discovery, then pass the returned URL to query_layer/layer_info for actual data. This implicitly directs when to use the tool. However, it does not explicitly state when not to use it or name alternatives like search_within or discover_tools, so it stops short of a 5.

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