export_dataset

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

Annotations declare readOnlyHint=true, and the description adds value by detailing the return format (CSV rows or GeoJSON FeatureCollection with specific fields) and confirming it returns the full file contents as text. No contradiction. Slight gap: no mention of error conditions or file size limits, but adequate for a simple export.

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 a single, well-structured paragraph. It starts with use case, gives example, then lists parameters and return info, and ends with exclusion guidance. Every sentence earns its place with no 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?

Given the tool's simplicity (1 optional parameter, no output schema, low complexity), the description covers everything: usage context, parameter details, return format and content, and sibling differentiation. No gaps.

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% coverage for the single 'format' parameter. The description compensates fully: it explains the parameter's purpose, lists valid values ('csv' default, 'geojson'), and ties to the example. This is exactly what the agent needs.

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 the verb (export), the resource (saved DC Hub shortlist), and differentiates from siblings like list_saved_sites and save_site. It explicitly says 'bulk-download path' and gives an example, making purpose unambiguous.

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?

The description explicitly states when to use ('when a user wants to pull their saved DC Hub shortlist OUT of the platform for offline analysis...'), includes an example, and provides when not to use by naming alternative tools (list_saved_sites, save_site). This is comprehensive guidance.

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