export_dataset

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

Description adds return format (file contents as text), supported formats (csv, geojson), and output fields (DCPI score, target MW, etc.). Annotations already declare readOnlyHint, idempotentHint, destructiveHint, so description complements well.

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?

Compact, front-loaded with use case. Every sentence adds value: example, param details, return content, exclusions. 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 simplicity (1 param, no output schema), description fully covers purpose, usage, parameter, return value, and exclusions. No missing info.

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 covers 100% of parameters (format). Description adds usage context: default csv, geojson for QGIS, and example usage.

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 tool exports saved DC Hub shortlist out of the platform for offline analysis or ingestion into another tool. Distinguishes from siblings list_saved_sites and save_site.

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 says when to use (user wants to export shortlist) and when not to (do not use to list sites or save new ones), with specific alternative tool names.

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