dataset_export

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

Annotations already establish readOnlyHint=true and destructiveHint=false. The description adds a real behavioral trait beyond them — the link is 'time-limited' — which matters for callers, though it does not say how long the link lasts or what happens if it expires.

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?

One dense sentence, front-loaded with the verb and result, then the acceptable inputs and the latest-vs-frozen distinction. Slightly long in listing three ref formats, but no wasted filler.

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?

No output schema exists, and the description compensates by stating the return is a download link. Both parameters are documented, and the version-selection behavior is covered; only link lifetime and failure modes are left unstated, which is a minor gap for a read-only lookup.

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%, so baseline is 3. The description slightly exceeds the schema: it restates the accepted dataset ref formats and clarifies that omitting version yields the latest export versus a frozen version, adding semantics beyond 'Saved version number.'

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?

States a specific verb and resource — retrieving a time-limited export download link for a dataset — plus the accepted reference formats. It reads clearly against siblings like export_create/exports_list, though it never explicitly names an alternative to disambiguate.

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?

Usage is implied: the agent understands this fetches a link rather than creating or listing exports. It adds a selection condition ('latest export or one frozen version') but gives no explicit when-to-use vs export_status/exports_list guidance and no prerequisites.

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