her_export_for_lidar

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

No annotations provided, so description carries full burden. Discloses output structure (easting/northing, fields) and bbox requirement. No contradictions. Adequate transparency for a read-like export tool.

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 intro, Args, Returns, and Tips sections. Slightly verbose with tips but each sentence adds value. No fluff.

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 5 params and no output schema, description covers purpose, parameters, output format, and a prerequisite workflow. Lacks error handling but sufficient for typical 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?

Schema coverage is 0%, but description fully explains all 5 parameters with formats, defaults, and usage context (e.g., bbox format, gateway_sites as output of her_enrich_gateway). Adds significant meaning beyond raw 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?

Description clearly states 'Export heritage assets for LiDAR cross-referencing' with specific resource and format (chuk-mcp-lidar). Distinguishes from siblings like her_export_geojson by focusing on LiDAR spatial matching format.

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 tips for LLMs (bbox required, use her_enrich_gateway first) which imply a workflow, but no explicit when-to-use vs alternatives like her_export_geojson or her_cross_reference.

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