vast_create_placement

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the action and adds a semantic clarification, but does not mention side effects, required permissions, return value, or any other behavioral traits beyond the basic create 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?

A single sentence that is front-loaded with the core action and immediately clarifies the resource. No wasted words or redundant information, making it an example of efficient description.

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 the tool having 13 parameters and complex relationships (e.g., zone/channel mutual exclusivity, required schedule), the description provides no lifecycle context, no mention of output/return value (since no output schema exists), and no differentiation from the very similar vast42_create_placement sibling. The rich schema partially compensates, but the description itself is too sparse for a tool of this complexity.

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 description adds no parameter-level semantics beyond what the schema already fully documents.

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 uses a specific verb ('create') and resource ('VAST placement') and the parenthetical clarifies exactly what that means ('assign a VAST ad item or campaign to a VAST zone or channel'). This distinguishes it from similar tools like vast_create_campaign_assignment and vast42_create_placement by clearly defining the placement concept.

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 the many sibling tools (e.g., vast42_create_placement, vast_create_campaign_assignment). It does not mention prerequisites, exclusions, or contextual cues that would help an agent decide between tools.

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