get_vast_auction_placements_report

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

No annotations are provided, and the description gives no behavioral details such as whether this is a read-only operation, what the report contains, whether it is generated asynchronously, or any side effects. The description carries the full burden and fails entirely.

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 extremely short, but this is under-specification rather than conciseness. A single sentence that merely restates the tool name does not 'earn its place' with informative value.

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 report tool with two parameters, no output schema, and no annotations, the description is completely inadequate. It does not explain what data the report returns, how preset/timezone affect results, or how to distinguish this from closely related reports.

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 input schema has 100% coverage: 'preset' is described as 'Date preset' and 'timezone' as 'Timezone'. The description adds no additional meaning, but the schema baseline of 3 applies since parameters are already documented. No further compensation is warranted.

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 'Get VAST auction placements report' is a near-verbatim restatement of the tool name. It names a verb and resource but adds no further distinguishing detail. Given many sibling report tools like get_vast_report and get_auction_placements_report, this fails to clarify what makes this report unique.

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?

No guidance is provided on when to use this tool versus alternatives such as get_vast_report or get_auction_placements_report. The description merely states the action without context, prerequisites, or exclusions.

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