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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a browse/read-style operation and a file type focus, but it doesn't explain filter precedence, search overrides, limit behavior, folder semantics, or output shape.

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 a single clean sentence with no filler, and it front-loads the core purpose. However, it is closer to a purpose tagline than a structured tool spec.

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 moderately paramterized tool with five optional inputs, no annotations, and no output schema, the description is too thin. It leaves agents without useful guidance on parameter interactions, filter behavior, and what a successful result looks like.

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%, so the description should compensate. It does not explain limit, folder_id, or type_filter beyond the vague 'image/video' hint, leaving three of five parameters underdocumented.

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 ('Browse'), a clear resource ('Google Drive'), the relevant content type ('creative image/video files'), and the downstream purpose ('upload to Meta'). This distinguishes it from sibling tools like adsap_list_dropbox_files and 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 implies the tool is for finding Google Drive creatives before a Meta upload, giving some context for when to use it. However, it does not explicitly state when not to use it or mention alternatives such as adsap_list_dropbox_files or adsap_list_creative_assets.

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