Get creative asset upload

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

readOnlyHint=true already establishes the safe-read profile, so the description's job is to add context. It does disclose the returnable status values (PROCESSING_MEDIA|ACTIVE|INVALID_MEDIA) and that an asset is produced, which is genuine added value, but it says nothing about read timing, eventual consistency, or auth requirements.

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?

One compact sentence with the resource front-loaded and the return shape trailing. Every clause carries information; no filler.

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 read-only, single-parameter lookup with no output schema, the description does the important work of naming the possible status states, but it omits what the id refers to and when in the upload lifecycle the call is appropriate. Adequate but with a clear gap.

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 0% and the single required parameter 'id' carries no description anywhere. The description never clarifies that the id is an upload id (as opposed to an asset id), which is the key ambiguity given the nearby get_creative_asset sibling.

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?

States a specific verb+resource ('Get a creative asset upload') and goes further by naming what is returned (status enum and resulting asset). It is distinguishable from list_creative_asset_uploads and get_creative_asset by resource, though it doesn't explicitly contrast with those siblings.

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 only says what the tool returns; it never says when to call it. There is no hint that this is the polling tool to use after reddit_ads_upload_creative_assets, nor any exclusion against list_creative_asset_uploads. Usage must be inferred entirely from context.

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