her_export_geojson

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

Discloses output format (GeoJSON FeatureCollection), coordinate system (WGS84), default and maximum values for max_results, and output_mode options. However, with no annotations, the description does not indicate whether the tool is read-only or destructive, nor does it mention potential errors 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?

Well-structured with a clear one-line purpose, followed by a short explanation, then a bulleted Arg list, Returns, and Tips. 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?

Covers all parameters, output format, and practical tips. Given the lack of output schema and the tool's moderate complexity, the description is nearly complete. It misses error handling or permission context, but overall provides sufficient information for effective use.

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?

Input schema has 0% description coverage, but the description's Args section fully compensates by explaining each parameter's purpose, format (e.g., bbox in BNG), default values, and options (e.g., output_mode). This provides complete semantic 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?

Clearly states the verb (export), resource (heritage assets), and output format (GeoJSON FeatureCollection). The description distinguishes this tool from the sibling her_export_for_lidar by specifying suitability for GIS tools like QGIS and Leaflet.

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?

Implies usage for exporting query results as GeoJSON, but does not explicitly state when to use this tool versus alternatives like her_export_for_lidar. The tips section provides some usage guidance (e.g., using bbox) but lacks exclusions or conditions.

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