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

With annotations present, the description still adds real value: it discloses the auth requirement (Cotlet API key with app access), states the operation is non-destructive to the deck and reaches no recipient, and ties format availability to the user's plan. It does not contradict readOnlyHint=false, since producing a file is a side effect.

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?

Front-loaded with the purpose, but the second sentence ('Exports one deck and returns a download link') is near-verbatim duplication of the first, and the plan/auth notes could be tightened into one sentence. Not poorly sized, just padded.

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 two-parameter export with no output schema, the description covers the key facts an agent needs: what it returns (a download link), that no recipient is notified, and that credentials are required. Missing only edge cases like format availability failures or link expiry.

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 100% and the enum for format is documented in the schema, so the schema carries the parameter burden. The description's 'Formats follow your Beautiful.ai plan' adds plan-tier context but no syntax or format guidance beyond the enum.

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 ('Export the deck') and says what comes back ('return a download link'), which is enough to distinguish it from siblings like create_share_link and duplicate_presentation. However, the opening two sentences restate the same fact, and it never names how it differs from the share-link tool for an agent deciding between export paths.

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 one piece of routing guidance — 'runs without asking' because the export is non-mutating and sends nothing — which is useful implied context. But there is no explicit when-to-use/when-not or comparison against the sibling share/duplicate tools.

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