Export Dataset

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavior beyond annotations: it returns the full file contents as text, describes the CSV and GeoJSON shapes, lists the included fields, and notes the PRO context of the operation.

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 dense but every sentence contributes: use case, example, parameter summary, return format, and exclusions. The most important usage guidance is front-loaded, and the sibling distinction is placed at the end where it completes the decision rule without cluttering the opening.

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?

For a single-parameter, read-only, idempotent export tool, this description covers usage triggers, format choices, output content, and alternatives. The output schema and annotations cover the remaining mechanical details, and no critical gap remains for an agent to call this tool correctly.

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 100% for the single format parameter, so the schema already carries the parameter meaning. The description adds extra value by specifying the default value ('csv' default), elaborating the GeoJSON use case (GIS tools like QGIS), and demonstrating usage with an example.

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 gives a specific verb-resource pair ('export saved DC Hub shortlist OUT of the platform') and clarifies the bulk-download nature. It is clearly distinguished from siblings by explicitly saying this is not the in-chat list tool or the save tool.

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?

It states exactly when to use it ('when a user wants to pull their saved DC Hub shortlist OUT...'), gives a concrete example, and explicitly names alternatives it should not be used for: list_saved_sites and save_site. Format selection guidance for CSV vs GeoJSON is also provided.

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