reddit get asset uploads

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

Annotations already declare the operation read-only, idempotent, non-destructive, and open-world, so the description is not responsible for basic safety disclosure. It adds important behavioral meaning beyond annotations by explaining that ACTIVE means 'media-ready, not advertising delivery,' which prevents misreading the status as ad delivery readiness.

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 compact sentence with the action and status caveat front-loaded, and every clause contributes: 'Poll processing' states the operation, 'through the profile' scopes it, and the ACTIVE caveat clarifies the result. There is no filler or redundant restatement of the title.

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 polling tool with three fully documented required parameters, an output schema, and rich annotations, the description covers the essential operation and clarifies the most likely misinterpretation of the ACTIVE status. It could optionally mention polling cadence or the relationship to the upload tool, but the schema and annotations carry the rest.

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 100%, and the schema already explains adAccountId, profileId, uploadIds, the t2_/a2_ formats, and the link to reddit_upload_creative_assets. The description only adds 'through the profile,' which does not materially extend parameter semantics beyond the schema.

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 uses a specific verb, 'Poll,' and a specific resource, 'processing of creative imports through the profile,' so the agent can tell this checks upload/import status rather than fetching finished creative assets. It does not name a sibling tool explicitly, but the resource and status semantics distinguish it sufficiently from reddit_get_creative_assets and reddit_list_ad_creatives.

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 word 'Poll' implies this is called after an upload or import submission and may be called repeatedly, but the description gives no explicit when-to-use condition, no when-not-to-use condition, and no named alternative. The schema's uploadIds field references reddit_upload_creative_assets, but that guidance is not in the description itself.

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