list_shared_links

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

No annotations provided, so description carries full burden. States read operation but omits critical behavioral details: pagination behavior, whether results include expired links, ownership scope (user-only vs team), and error handling when no links exist.

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, front-loaded with action. No redundancy, though brevity borders on underspecification given 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?

Minimally adequate for a single-parameter list operation. Covers core functionality and optional filter. Lacks output format details, but acceptable given no output schema and low complexity.

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% with path described as 'Optional path to filter shared links'. Description maps 'Dropbox file/folder' to the path parameter but adds no semantic detail beyond schema (format, examples, path requirements). Baseline 3 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?

Clear verb 'List' with specific resource 'shared links' and scope (file/folder or all). Implicitly distinguishes from create_shared_link (create vs list) and list_folder (links vs contents). Missing explicit Dropbox context or differentiation from search.

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?

Implies optional filtering via 'or all shared links' but lacks explicit when-to-use guidance. No mention of when to prefer this over search/list_folder or prerequisites (e.g., needing file access permissions).

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