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

Annotations only say it is destructive, non-idempotent, and open-world; the description goes well beyond by disclosing that the URL is returned exactly once and is unrecoverable, that expiry ranges from one minute to thirty days (absent = no expiry), that indexable defaults to off so links stay unlisted, and that no credits are spent. The one-shot/unrecoverable nature is critical and is not in any structured field.

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 most important constraint (single-use URL, hand it over now) is front-loaded, and the rest is packed into two dense sentences with little waste. It is long but nearly every clause conveys a distinct rule, so only mild trimming is possible.

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?

An output schema exists, so return structure need not be explained, and the description still covers the one-shot return behavior, expiry semantics, most settings, default privacy behavior, and cost. For a 3-param, nested-object, destructive tool this is sufficient to call it 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 description coverage is only 33%, so the description must compensate, and it largely does: it explains expires_in_seconds' bounds and no-expiry default, and maps most settings fields (title, caption, download, made_with as provenance level, theme, indexable) to their meaning. It leaves remix, branding, and view_count unmentioned, so it stops short of fully covering the surface.

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 opens with a specific verb ('Mint a public permalink') and enumerates exactly what can be shared (a ready generation, a verified upload, or a whole group). That scope, plus the same-turn handoff note, clearly separates it from siblings like get_download_url, list_share_links, and revoke_share_link.

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 gives clear operating context — ask before sharing on someone else's behalf, and hand the URL to the user in the same turn — and hints at the revoke alternative ('nothing can recover it later, only revoke it'). It never explicitly names a sibling to prefer for other cases, so 4 rather than 5.

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