her_enrich_gateway

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

Discloses slowness (1-2 minutes), result filtering (only records with valid coordinates), and default behaviors. Lacks explicit safety statement but overall reveals key behavioral traits beyond the schema.

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?

Well-structured with sections, but some redundancy in tips (e.g., 'use before cross-reference' repeated). Still efficient and front-loaded with purpose.

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?

Explains return value shape (records with BNG coordinates) and relationship to her_cross_reference. Lacks output schema but provides enough context for effective use. Could detail record format, but sufficient given complexity.

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 'Args' section explains all six parameters, including defaults and purpose, fully compensating for the 0% schema description coverage. Tips add practical guidance for fetch_details and output_mode.

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 'Fetch Heritage Gateway records with resolved coordinates', specifying verb (Fetch) and resource (Heritage Gateway records). It distinguishes from sibling her_search_heritage_gateway by emphasizing coordinate resolution and cross-referencing use.

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 advises to use before her_cross_reference and suggests running her_search_monuments and her_search_aerial in parallel for comprehensive coverage. Provides clear when-to-use and alternatives.

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