get_placement_forecast

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

No annotations are provided, and the description simply restates the tool's name without detailing any behavioral aspects such as whether it is read-only, what data it returns, or how the preset and timezone parameters affect the forecast. It offers no added context beyond the tool 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 concise sentence with no fluff. It is front-loaded and short, but it is also minimal, providing only the essential phrasing without any extra contextual structure. This earns it a strong but not top score.

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 2 parameters, no annotations, and no output schema, the description does not provide enough context. It fails to explain what the placement forecast report contains, how to use the preset/timezone, or what the response looks like, making it inadequate for an AI 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 schema covers both parameters (preset and timezone) with brief descriptions. The tool description does not add any semantic detail about the parameters, so it relies entirely on the schema. Given 100% schema coverage, a baseline score of 3 is appropriate.

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 ('Get') and resource ('placement forecast report'), making the core action clear. However, it does not distinguish this from sibling forecast tools like get_display_forecast or get_vast_forecast, so it lacks 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 provides no guidance on when to use this tool, what type of placement forecast it produces, or how it compares to other forecast/report tools. No exclusions or alternatives are mentioned.

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