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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing the async PENDING_UPLOAD return, the plan-based size ceilings (Basic 500 MB / Pro 1 GB), that private/internal URLs are blocked, and the guest-mode limits without an API key (100 MB, 24-hour link). These are real constraints an agent cannot infer from structured fields.

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 correctly — routing advice and the async warning come first, caveats last. However, the final clause ('a key raises the limits and lets you sell') is compressed into a run-on sentence with a missing space after 'lifecycle.', which slightly hurts readability.

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 an output schema existing, the description still explains the salient return state (PENDING_UPLOAD) and the polling obligation, plus auth-mode-dependent limits. Nothing an agent needs to invoke this correctly or interpret the immediate result is missing.

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 100%, so the baseline is 3, but the description adds cross-parameter context the schema does not: the no-key guest mode is what makes payoutAddress meaningful and idempotencyKey irrelevant. That clarifies the operating mode that governs two optional params, though it does not add anything beyond the schema for url/fileName/pricePerDownload.

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 the specific verb+resource ('Low-level upload from URL') and immediately distinguishes itself from siblings by naming 'transfer' as the preferred tool and 'get_upload_status' as the required follow-up. An agent knows exactly what this does and does not do without opening the schema.

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?

Explicit routing guidance: prefer 'transfer' because it polls automatically, and use this one 'only when you need explicit control over the upload lifecycle.' It also states the required follow-up action (poll get_upload_status yourself), so both when-to-use and what-happens-next are covered.

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