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

Annotations already declare the key profile: not read-only, open-world, non-idempotent, non-destructive, plus an output schema. The description adds one genuinely useful fact beyond that — the PDF is temporary — and implies an outbound fetch of a public URL. It says nothing about what 'temporary' means (lifetime, expiry), whether repeated calls with the same source produce new artifacts, or what the branding source is.

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 front-loaded sentence with no filler or redundancy; the two output artifacts and two input modes are stated immediately. It is arguably too terse for a tool with three parameters and a generated artifact, but nothing in it is wasted.

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 values need not be explained. However, for an open-world, non-idempotent creation tool the description leaves open what 'temporary' means, whether the call is billable/rate-limited, and what branding is applied — gaps the annotations do not fill.

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%, so 'n', 'title', and 'source' constraints (clamping, byte caps, title-only-with-text) are already fully documented in structured fields. The description only echoes that source can be a URL or text, adding no new parameter semantics. 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) plus two concrete artifacts (branded carousel, temporary PDF) and the accepted input forms (public URL or text). An agent knows exactly what the tool produces, though 'branded' is left undefined.

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?

No statement of when to use this tool, when not to, or what prerequisites exist (e.g. whether the URL must be reachable, whether branding is configured elsewhere). There are no siblings to differentiate against, but the description still offers no situational guidance.

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