Create post (structured)

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

Annotations already declare it is a mutation (readOnlyHint=false) and open-world. The description adds substantial context beyond them: the operation is asynchronous, results are retrieved via polling, and media is fetched by Reddit from public URLs. Failure semantics and any rate limits remain undisclosed.

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?

Three tight sentences, front-loaded with the action and async nature, then the follow-up path. No filler; every sentence carries actionable information.

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?

With no output schema, the description correctly explains how the return value is obtained (poll for the post_id) and covers the media-sourcing behavior. For an async mutation tool this is nearly complete, though it omits error handling and whether fields like allow_comments have defaults.

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 coverage is 50%; the 'data' object is exhaustively documented in the schema itself (creative types, call_to_action enums, required fields), while profile_id carries no description. 'On a profile' lightly explains profile_id but the description contributes essentially no parameter detail beyond what the schema provides.

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 ('Create an ad post on a profile') and adds scope via 'structured' and 'asynchronously'. It hints at the workflow, but does not explicitly differentiate from close siblings like reddit_ads_create_post or reddit_ads_create_poster_job, leaving the agent to infer the distinction.

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?

Clear downstream workflow is given: poll reddit_ads_get_post_job until SUCCESS, then use the post_id with reddit_ads_create_ad. That routes the agent across the async boundary well. It stops short of stating when to choose this tool over the non-job create siblings.

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