her_search_monuments

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

With no annotations, the description carries full burden. It discloses that NHLE only contains designated assets and advises additional searches for undesignated sites. It also mentions pagination (offset), result limits, and output modes, though it stops short of describing rate limits or exact response shape.

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 organized into an opening summary, Args list, Returns line, and a 'Tips for LLMs' section. Each section adds distinct value, and the text is front-loaded with the primary purpose before moving to parameters and guidance.

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?

Despite having no output schema or annotations, the description covers the core query capabilities, parameter semantics, default behaviors, and important coverage limitations. It also points to follow-up tool usage, making it self-sufficient for an agent to select and invoke this tool.

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?

Even though the JSON schema's property descriptions are absent, the description's Args section gives every parameter meaning: bbox format with example, radius_m requires lat/lon, max_results bounds (1-2000, default 50), offset for pagination, and output_mode choices. This fully compensates for the 0% schema coverage.

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 opens with a specific verb and resource: 'Search scheduled monuments by location, name, or description.' It also names the exact data source (NHLE) and distinguishes from sibling search tools by focusing on scheduled monuments.

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?

Provides explicit when-to-use guidance: bbox for area searches, lat/lon+radius for point searches, name for text searches. It also names alternatives and complements, including her_get_monument for follow-up and her_search_heritage_gateway/her_search_aerial for undesignated coverage.

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