Draft Reddit ad changes

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

Annotations indicate readOnlyHint=false and destructiveHint=false, meaning it's a mutating but non-destructive operation. The description explains that the headline and body cannot be edited, and that click_url is verified reachable, adding behavioral context beyond annotations. It also clarifies the preview-confirm workflow but doesn't detail side effects if confirm_and_apply is not called.

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 concise, with the core purpose and editable fields in the first sentence, followed by critical constraints and workflow in the subsequent sentences. Every sentence adds value without redundancy.

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?

Despite an output schema, the description does not explain the return value or the outcome of the draft action. It mentions preview and confirm_and_apply but not what the response contains. This is a minor gap for a draft tool, but for an agent to validate success, it might need more. The core workflow is covered, so it's slightly above average.

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 0%, meaning the description must add meaning to parameters. It identifies click_url, name, and allow_comments, but doesn't explain ad_account_id, which appears in the schema. It doesn't clarify what allow_comments accepts (true/false/null) or the purpose of ad_account_id, missing an opportunity to compensate for low schema coverage.

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 clearly states the tool's function: drafting changes to a Reddit ad, specifying the editable fields (name, click_url, allow_comments) and the workflow. It distinguishes itself from siblings by mentioning draft_reddit_ad for new copy and pause_old_ad, making its specific purpose clear.

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?

It explicitly states when to use this tool (drafting changes to existing ads) and when not to (new copy should use draft_reddit_ad and pause the old ad). It also explains the preview and confirm_and_apply workflow, providing clear context for usage.

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