draft_create_campaign_assignment

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

No annotations are provided, so the description carries the full burden. It simply states 'Create' without disclosing that this creates a draft (non-live) assignment, that campaign and advertisement are auto-resolved, or any side effects. The 'draft' qualifier is in the name but not explained behaviorally.

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 concise sentence that front-loads the action. It contains no fluff, though it is minimal. For a simple CRUD operation, this length is acceptable, but it lacks explanatory context that would make it more useful.

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?

The description is incomplete given the surrounding draft_* tool ecosystem. It does not explain what a draft campaign assignment is, how it relates to draft campaigns and ad items, or how it fits into the draft workflow (e.g., draft_save_campaign). The schema provides param definitions but not domain context.

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?

The schema description coverage is 100%, and each parameter has a clear description. The tool description adds no parameter info beyond the schema, so with high schema coverage, the baseline of 3 is appropriate. The 'draft' object's auto-resolution is noted in the schema, not the description.

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 'Create a new draft campaign assignment', specifying the verb and resource. It is slightly more than the name itself, but it does not explain what a 'draft' assignment is or how it differs from the non-draft create_campaign_assignment sibling, so it lacks sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that it is for draft workflows, nor does it contrast with create_campaign_assignment or draft_update_campaign_assignment. The description provides no usage context or exclusions.

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