Read file (text)

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

The description adds valuable behavioral context beyond the readOnlyHint annotation: it returns UTF-8 text, enforces a size guard (DROPBOX_MAX_READ_BYTES, default 5 MB), and points out the large/binary file limitation. This is precisely the kind of runtime behavior an agent needs to know.

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?

The description is compact and front-loaded: the action and return type come first, followed by the size guard and the alternative-tool routing. Every sentence earns its place and no filler is present.

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 one-parameter tool with a fully described schema, the description covers the output format, the size limitation, and the appropriate alternative for unsupported files. No critical operational context 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 description coverage is 100%, so the schema already documents the path parameter thoroughly, including an example and the empty-string root convention. The description itself does not add further parameter-level detail, so the baseline of 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 clearly states the verb ('Download and return contents as UTF-8 text') and the resource ('a file'), with concrete use cases like docs, notes, code, and csv. It also distinguishes itself from the sibling dropbox_get_temporary_link by emphasizing text retrieval versus link creation.

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 explicitly names the alternative tool for large or binary files — dropbox_get_temporary_link — and provides the condition that should trigger that alternative. This gives an agent clear routing guidance for when this tool is and isn't appropriate.

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