her_search_monuments

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

With no annotations, the description carries the burden. It discloses that it queries NHLE, returns matching monuments with location and metadata, and implies it is a read operation (search). However, it does not explicitly state it is read-only or mention rate limits. Still, it adequately conveys the tool's behavior.

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 well-structured with a concise summary, detailed Args list, Returns section, and Tips for LLMs. It is front-loaded with the purpose. 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 9 parameters, no required ones, and no output schema, the description fully explains parameter usage, return value (matching monuments with location and metadata), and provides cross-references to sibling tools. It is comprehensive for an LLM to use 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 0%, so the description must compensate. It provides detailed explanations for all 9 parameters, including formats like 'bbox as xmin,ymin,xmax,ymax in BNG (EPSG:27700)', radius in metres, max_results range, and output_mode values. This adds significant meaning beyond the bare schema.

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 'Search scheduled monuments by location, name, or description.' It specifies the resource (scheduled monuments) and the actions (search). It distinguishes from siblings by noting that NHLE only contains designated assets and suggests other tools for undesignated sites.

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 explicit when-to-use guidance for each parameter (bbox for area, lat/lon+radius for point, name for text). It includes tips for LLMs, such as following up with her_get_monument, using her_count_features first, and alternatives for undesignated sites. This clearly differentiates usage from sibling tools.

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