get_vast_report

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

With no annotations, the description carries the full burden of behavioral disclosure, but only states that it gets a report. It doesn't mention whether this is a read-only operation, what data is included, whether it supports filtering or aggregation, or any other behavioral traits. This is a significant gap for a tool with 12 parameters.

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 one concise, front-loaded sentence with no wasted words. It earns its place, though it could benefit from more detail given the tool's complexity; it is not overly verbose.

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 tool with 12 parameters, many sibling report tools, and no output schema, this description is incomplete. It doesn't explain report types, filtering options, or what the response contains, leaving the agent without enough context to use the tool effectively.

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 with clear descriptions for all 12 parameters, so the schema already provides strong parameter semantics. The description itself adds no extra meaning, but the baseline of 3 is appropriate given the high schema coverage.

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 video advertising report' uses a specific verb and resource, and clarifies that it concerns VAST video advertising. However, it doesn't specify what kind of report (e.g., overview, breakdown by campaign) or what metrics it returns, making it only somewhat distinguishable from sibling report tools.

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 alternative report tools like get_display_report, get_vast_forecast, or get_vast_geo_summary_report. The description gives no context for choosing this specific report.

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