create_reddit_campaign

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

Annotations provide destructiveHint=true, indicating a write operation. The description adds value by specifying 'community-based advertising,' which hints at targeting subreddits or interests, aligning with parameters. However, it doesn't disclose additional behavioral traits like authentication needs, rate limits, or error handling beyond what annotations cover.

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, efficient sentence that front-loads the core purpose without unnecessary words. It earns its place by clearly stating the tool's function, making it easy to parse and understand quickly.

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?

Given a destructive operation (annotations), 5 parameters with full schema coverage, and no output schema, the description is adequate but lacks depth. It doesn't explain return values, error cases, or integration context, leaving gaps for an agent to infer behavior in a campaign creation scenario.

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%, so parameters are well-documented in the schema. The description adds minimal semantics by implying 'community-based advertising' relates to subreddits/interests, but doesn't provide extra details like format examples or constraints beyond the schema. Baseline 3 is appropriate given high 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 action ('Create') and resource ('Reddit Ads campaign') with the specific context of 'community-based advertising.' It distinguishes from siblings like create_meta_campaign or create_linkedin_campaign by specifying the platform (Reddit), but doesn't explicitly differentiate from other Reddit-specific tools (none exist in 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 provides no guidance on when to use this tool versus alternatives (e.g., other campaign creation tools like create_search_campaign or create_display_campaign). It lacks context about prerequisites, target scenarios, or exclusions, leaving the agent with minimal usage direction.

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