vast_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 only states the core creation behavior and adds no context about side effects, idempotency, validation, active default (though the schema does), or response format. This is a minimal disclosure for a write operation.

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 sentence of 14 words, front-loaded with the core action 'Create a VAST campaign assignment'. It has no redundant information or repetition of schema fields, making it efficient for the tool's simplicity.

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 create tool with 3 parameters and no output schema, the description gives the core purpose but omits any mention of return value, prerequisites, or validation behavior. Given the existence of several sibling create tools, more context would help distinguish this specific version, but the schema covers parameter descriptions adequately.

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 the baseline is 3. The phrase 'assign an ad item to a campaign' adds some context by mapping ad_item and campaign to entities, but this is already evident from the schema's parameter names and descriptions. No additional syntax, constraints, or relationships are provided.

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 specifies the verb 'Create' and the resource 'VAST campaign assignment', with the parenthetical 'assign an ad item to a campaign' clarifying the entity. It differentiates from read/update/delete siblings, but not from similar create variants like vast42_create_campaign_assignment or draft_create_campaign_assignment.

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 the draft or vast42 variants, nor any context about prerequisites such as requiring existing ad items and campaigns. The description is purely declarative with no exclusions, alternatives, or conditions.

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