her_nearby

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

No annotations are provided, so the description carries the full burden. It discloses that it searches NHLE, returns sorted by distance, and includes tips about coordinate systems and result details. It does not explicitly address permissions or side effects, but the read-only nature is implied. Slight lack of explicit non-destructive assertion.

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 sections for Args, Returns, and Tips. It is slightly lengthy but each sentence adds value. The main purpose is front-loaded, and 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 no output schema, the description adequately describes returns. It accounts for the complexity of 7 parameters with coordinate system choices and links to sibling tools. It provides comprehensive guidance for a complete search workflow.

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 has 0% description coverage, but the description provides extensive parameter documentation in the Args section, including coordinate alternatives, default values, and usage constraints (lat/lon vs easting/northing). This adds critical meaning beyond the 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 the verb 'Find' and resource 'NHLE heritage assets near a single point'. It specifies the spatial search within a radius and sorting by distance. It also distinguishes from sibling tools by mentioning Scottish and aerial alternatives.

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 explicitly tells when to use this tool (for NHLE in England) and when not (use her_search_scotland for Scotland, her_search_aerial for aerial features). It also advises calling both for comprehensive results, providing clear alternatives and context.

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