her_search_scotland

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

No annotations provided, so description carries full burden. It discloses that it queries NRHE, covers terrestrial sites, and mentions MapServer max of 1,000 records per request. It also describes return format. However, it does not explicitly state that the tool is read-only or mention any authentication or rate limits.

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 somewhat lengthy but well-structured with sections: summary, args, returns, tips. Every sentence adds value, though tips could be slightly condensed. The structure aids readability.

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 10 parameters, no output schema, and many sibling tools, the description is highly complete. It covers all parameters, provides usage guidance, mentions limits, and cross-references related tools. The return description is brief but adequate.

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 0%, and description compensates fully. Each parameter is explained with clear meaning (e.g., 'Site name keyword (partial, case-insensitive)'), examples for site_type, and format for bbox. It also explains usage constraints like lat/lon requiring radius_m.

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 Scottish NRHE records (320,000+ sites from Canmore). It specifies the resource (terrestrial archaeological sites, monuments, and buildings in Scotland) and distinguishes from sibling tools like her_search_scotland_designations.

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?

Explicitly provides when-to-use guidance: mentions that for designated assets only, use her_search_scotland_designations, and for cross-border queries near England/Scotland border, also run her_search_monuments and her_search_aerial. Also includes tips for site_type keywords and max results limit.

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