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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the read-only nature ('Browse') and the output (dropbox_path), but it does not mention pagination, rate limits, authentication, or whether the returned files are filtered by default. The phrase 'creative image/video files' could imply a filter, but the schema has a type_filter parameter allowing ALL, so the default behavior is ambiguous. More disclosure would be beneficial.

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, no fluff. The first sentence states the purpose and scope, the second states the output and integration. Information is front-loaded and every word earns its place.

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 listing tool with 4 optional parameters and no output schema, the description provides the essential purpose and the key output field (dropbox_path). However, it does not explain pagination, sorting, default filters, or error behavior. Given the absence of annotations and an output schema, more context would be needed for an agent to use the tool correctly in all scenarios. The integration hint is helpful but not sufficient for full completeness.

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 50% (folder_path and search_query have descriptions, limit and type_filter do not). The tool description does not add parameter-specific meaning beyond what the schema already provides. It only mentions the output path and its use in uploads, which is not parameter-related. Since coverage is partial but not zero, a baseline of 3 is appropriate, but the description could have compensated for the missing parameter details.

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 'Browse', the resource 'Dropbox', and the purpose 'creative image/video files to upload to Meta'. It also explicitly mentions the output (dropbox_path) and its compatibility with the sibling tool adsap_upload_creative, which distinguishes it from other listing tools like adsap_list_drive_files or adsap_list_creative_assets.

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?

The description provides clear context for when to use the tool (when you need Dropbox files for Meta uploads) and even names the integration point (adsap_upload_creative). However, it does not explicitly exclude alternatives like Google Drive or Meta assets, leaving some inference to the agent. Still, the purpose and the mention of the downstream tool offer strong guidance.

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