Download private brand logos

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

With annotations covering the safety profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true), the description goes well beyond them: fixed CDN, no redirects, no Bearer forwarding, no hotlink evasion, no retries, a 5 MiB per-file cap, stop-on-failure semantics, and retention/reporting of completed versus reserved files. That is rich operational context an agent could not derive from the structured fields, and nothing contradicts the annotations.

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 dense sentences, front-loaded with the core action and scope, and every clause carries distinct information (caps, security constraints, failure handling). The phrasing is jargon-heavy and occasionally awkward ('original credentialed Brand API logo src downloads'), which slightly hurts scannability but not economy.

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 9-parameter, file-writing, open-world tool with no output schema, the description covers the essentials: prerequisite confirmation, per-download caps, network/auth constraints, and partial-failure behavior with reporting. It stops short of clarifying quota consumption or the directory-prerequisite detail, but the picture is largely complete.

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 78%, close to the high-coverage band, so the schema already documents most parameters (identifier formats, cachedOnly quota note, account isolation). The description adds the 'at most five' cap and the confirm requirement, but does not touch allowNsfw, identifier_type, or format_preference, so it neither compensates nor detracts. Baseline 3 is appropriate.

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 names a specific verb and resource ('download'), and pins down the scope precisely: one brand lookup plus up to five credentialed Brand API logo downloads into a local directory. It is clearly a write-to-disk operation, distinguishable from read-style siblings, though it never names an alternative such as get_logo_url for the URL-only case.

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?

Usage is only implied: 'Confirmed one brand lookup' signals that the confirm parameter must be set, and the file-download framing suggests local writes rather than the URL-only path. There is no explicit 'use this instead of get_logo_url' routing or stated prerequisite (e.g. that output_dir must pre-exist), so the agent must infer when this tool is the right choice.

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