Download private brand logos

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

Annotations flag a destructive, open-world, non-idempotent write, and the description adds substantial traits on top: files land only in an owner-private directory, 5 MiB per-file cap, fixed CDN with no redirects, no Bearer forwarding, no hotlink evasion, no retries, and halt-on-failure with completed/reserved files retained and reported. This is far richer than the structured hints alone.

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 sentences, purpose front-loaded, no filler. The second sentence is a dense slash-delimited constraint run that is efficient but slightly hard to parse; still, every clause carries a distinct constraint.

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 destructive, open-world file-writing tool with no output schema and high schema coverage, the description covers failure semantics, size limits, network restrictions, and reporting of partial results. The main omission is explicit routing relative to sibling logo/URL tools.

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 coverage is high (78%), so the baseline is 3, but the description still adds meaning: it ties 'confirmed' to the confirm flag, 'owner-private directory' to output_dir, and 'at most five' to the max_files cap. It reinforces rather than merely repeats schema content.

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 (download) and resource (brand logos) plus the operational scope: one confirmed brand lookup yielding at most five logo src files. It's clear what happens, but it never names the obvious alternative (get_logo_url) or distinguishes itself from sibling prefetch_brand, so an agent must infer the difference.

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?

Implied usage is clear (fetching logo binaries to an owner-private directory), and 'Confirmed' hints that the confirm flag must be set for this exact action. However there are no explicit when-to-use/when-not rules and no routing against get_logo_url or prefetch_brand, so the agent gets context but not guidance.

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