list_folder

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

No annotations provided, so description carries full burden. Fails to disclose critical behaviors: whether listing is shallow or recursive, pagination limits for large folders, error handling for invalid paths, or that this is a read-only operation.

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?

Single sentence of nine words is efficient and front-loaded with the action. No wasted words, though brevity leaves significant behavioral context undocumented given the lack of annotations.

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?

Covers basic purpose adequately given the simple single-parameter input. However, with no output schema and no annotations, the omission of behavioral details (pagination, recursion depth, return structure) creates gaps that the description should have addressed.

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 has 100% coverage with clear description for 'path' parameter. The description implies the directory context but adds no syntax details, validation rules, or formatting requirements beyond what the schema already provides.

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?

Clear verb ('List') and resource ('files and folders in a Dropbox directory') immediately conveys scope. However, it does not explicitly differentiate from the sibling 'search' tool or indicate this lists contents of a specific directory only.

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?

Provides no guidance on when to use this versus 'search' (for querying across folders) or 'get_metadata' (for specific file details). No mention of prerequisites like path existence or permissions.

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