get_auction_placements_report

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 tool name in sentence form and adds no information about read-only nature, output format, pagination, or side effects. The agent is left to infer everything from the name.

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, short sentence with no filler or redundant wording. It is well-structured and front-loaded, though it may be too terse to be genuinely informative.

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?

With no output schema, no annotations, and minimal parameter descriptions, the tool requires more context than this description provides. It doesn't explain what statistics are included, how preset/timezone affect the report, or what the response looks like. Given the many sibling report tools, this lack of context makes it hard for an agent to select and invoke correctly.

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 describes both parameters (preset and timezone) at 100% coverage, so the baseline is 3. The description itself adds no extra meaning about these parameters, such as allowed values or format, but per the rubric the schema coverage keeps this at a passing level.

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 clear verb 'Get' and identifies the resource as an auction placement statistics report, making the basic purpose understandable. However, it doesn't distinguish this tool from the similarly named sibling 'get_vast_auction_placements_report' or clarify what 'auction placements' entails, so it falls short of full 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?

The description gives no guidance on when to use this tool versus the many report tools in the sibling list, such as get_vast_auction_placements_report or get_display_report. There are no context cues, prerequisites, or exclusions, leaving the agent without decision support.

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