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

With no annotations, the description carries the full behavioral burden. It usefully discloses a non-obvious quirk – Drive only shows files the user picked in the web app, so an empty list does not mean an empty Drive – but omits permissions, pagination behavior tied to 'limit', and return format.

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 tightly written sentences: the purpose is front-loaded and the empty-list caveat follows. Every sentence earns its place with no filler, though the caveat sentence is dense.

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 list tool with no annotations, no output schema, and 5 under-documented parameters, the description covers purpose and one key caveat but leaves return shape, pagination, and folder/search interaction unexplained. Adequate but with clear gaps.

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 only 40% (folder_path and search_query are documented; limit, folder_id, and type_filter are not), so the description should compensate but instead mentions no parameters at all. It adds zero meaning beyond the schema for a 5-parameter tool.

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 states a specific verb and resource ('Browse Google Drive for creative image/video files') and scopes the purpose to Meta uploads. It is clearly distinguishable from the sibling adsap_list_dropbox_files by naming Drive, though it never explicitly contrasts with it. Clear but no active sibling differentiation.

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 phrase 'to upload to Meta' implies the workflow context (fetching creatives for the Creative Upload page), giving implicit usage guidance. However, it never states when to use this versus alternatives like adsap_list_dropbox_files or adsap_list_creative_assets, nor when folder vs search_query browsing is appropriate.

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