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, so the safety profile is clear. The description adds value by disclosing the exact return fields (name, summary, record_count, owner/org, Feature Service url) and how the url should be used downstream, 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, front-loaded with the main purpose, and contains zero redundant or filler content. It efficiently packs scope, return fields, and downstream tool references.

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/discovery tool with no output schema, the description enumerates the return fields and explains how to continue the workflow with query_layer/layer_info. Combined with the fully documented schema and strong annotations, an agent has everything needed to select and invoke the tool correctly.

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%: all three parameters (limit, query, org_id) have descriptive text. The description adds minimal parameter-specific meaning beyond the schema (only mentions keyword search generically), so the baseline 3 applies.

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 uses the specific verb 'Search' with a clear resource: 'City of Norman GIS open geospatial datasets'. It lists example dataset types and explicitly states what is returned, distinguishing it from sibling tools like query_layer and layer_info by positioning it as the discovery step.

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 clearly implies a workflow: search for datasets, then pass the returned url to query_layer or layer_info. This gives contextual guidance on when to use this tool versus data-querying siblings, but it does not explicitly state when not to use it (e.g., if a dataset URL is already known).

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