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

Annotations already declare safety (read-only, idempotent, non-destructive). The description adds the return structure (name, summary, record_count, owner/org, Feature Service URL) and a clear behavioral note about passing the URL to query_layer/layer_info. It does not discuss potential result count limits or edge cases, but the added context 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, front-loaded with the primary action and then adding optional scoping and return details. Every sentence contributes meaning, with no fluff or 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?

For a search tool with 3 parameters and no output schema, the description covers the core behavior, optional scoping, return fields, and downstream usage. It does not describe edge cases (like no results) or exact response format, but the mention of downstream tools and fields gives sufficient context for an agent to use it effectively.

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%, so the schema already explains all three parameters. The description mentions org_id as 'an ArcGIS orgId' and scoping, but this largely restates the schema's description ('Optional ArcGIS orgId to scope results to one publisher'). No additional semantic value beyond the schema 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?

The description states a specific verb ('Search'), a resource ('ArcGIS Hub catalog of open government geospatial datasets'), and the scoping mechanism (keyword, optionally org_id). It distinguishes itself from siblings by explicitly mentioning query_layer and layer_info as downstream recipients of the returned URL.

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?

It clearly explains when to use the tool: for keyword-based discovery of geospatial datasets, optionally scoped to an organization. It also gives implicit guidance on next steps by pointing to query_layer/layer_info for further data access. However, it does not explicitly state exclusions (e.g., 'when not to use' or compare with search_within), so it falls 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.