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

Beyond the readOnlyHint/destructiveHint annotations, the description discloses two non-obvious behaviors: the link expires after 15 minutes and the archive includes form records as CSV and uploaded files. It still omits whether the export is synchronous or takes time, and whether unpublished content or size limits apply.

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?

Two tight sentences, zero filler, with the core action and expiry front-loaded and the user-facing follow-up last. Nothing could be removed without losing information.

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 tool with no output schema, the description covers what is produced, how long the link lasts, and what to do with it. Minor gaps remain around export timing and whether drafts are included, but an agent can call this correctly as written.

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?

Only one parameter, and the schema already documents it at 100% coverage as a site slug (e.g. "kopitiam-muar") or id. The description adds nothing about the site argument, so the baseline 3 applies.

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 ('Create a download link') plus the exact resource and scope ('a zip of the whole site'), and enumerates the bundle contents (pages, assets, form records CSV, uploaded files). This clearly separates it from siblings like get_upload_link (inbound upload) and preview_site (browsing).

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 closing sentence 'Give the link to the user' is a useful post-call instruction, implying the tool is used when a user wants a full-site backup/download. However, it never states when not to use it or points to alternatives such as preview_site or per-page reads for narrower needs.

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