Download Unsplash+ asset

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

With no annotations, the description carries the full burden. It discloses that authentication via the website UI is required and that an audit receipt is written, which is useful. However, it does not mention failure modes, idempotency, or other side effects beyond the receipt.

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?

A single concise sentence efficiently communicates the primary action and a key side effect. No filler or redundant information, every word earns its place.

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?

Despite the low complexity, the description omits parameter meanings and any return or failure behavior. The audit receipt is mentioned but not explained, leaving the description incomplete for a reliable invocation.

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 0% and the description does not mention assetSlug or filename. Since the schema provides no descriptions and the tool text fails to compensate, the agent receives no semantic information about parameters needed for correct invocation.

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 uses a specific verb 'Download' with a clear resource 'Unsplash+ image' and adds an additional action 'write an audit receipt', which distinguishes it from sibling tools like get or search. It is immediately clear what the tool does.

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 guidance is provided on when to use this tool versus alternatives like unsplash_plus_get or unsplash_plus_search. The mention of 'authenticated website UI' implies a prerequisite but does not offer clear context for selection or exclusions.

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