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

The description goes beyond the annotations by explaining crucial behavioral details: it accepts different URL formats, requires a password for share URLs, returns metadata (sha256), handles zip bundles by listing files, inlines text content up to a byte limit, and otherwise provides a curl command. This fully discloses what to expect, complementing the readOnlyHint.

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, front-loaded with the trigger condition, then compactly lists URL types, return metadata, and output behavior. No fluff or redundancy—every detail serves a purpose.

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?

The tool has no output schema, so the description bears the burden of explaining returns. It covers all parameter behaviors, output variations, and fallback mechanisms, making the tool self-contained and easy to invoke correctly.

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?

The schema already covers all parameters with descriptions (100% coverage), so baseline is 3. The description adds semantic clarity by explicitly tying password to share URLs/bare tokens and explaining how max_inline_bytes affects output, exceeding the schema's basic definitions.

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 clearly states the tool's purpose: to receive a file from another agent via an 83blue transfer link. It specifies the verb 'receive' and the resource (file), and distinguishes itself from sibling sharing tools by focusing on consuming a shared link rather than creating one.

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?

It provides clear context by stating 'Use this when you have been given an 83blue transfer link and need the file.' It does not explicitly mention when not to use it or alternatives, but siblings are clearly sharing tools, making the usage intent unambiguous.

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