vast_get_ad_item

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

With no annotations provided, the description carries the full burden of disclosing behavior, but it only says 'Get details' without mentioning whether the operation is read-only, what response format to expect, or any permission/error considerations. The read intent is implied but not elaborated.

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, front-loaded sentence with no filler words. It efficiently communicates the core purpose without redundancy.

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 simple single-parameter get operation, the description is minimally adequate, but it lacks optional context such as what fields are included in 'details', behavior when the ID is not found, and relationship to sibling tools. Since there is no output schema and no annotations, a bit more explanatory detail would make it more complete.

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 already documents the 'id' parameter with a description ('VAST ad item ID') and 100% schema coverage, so the description adds no additional parameter meaning beyond the schema baseline. The word 'specific' reaffirms the need for an ID but adds no new semantic detail.

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 a clearly defined resource 'details of a specific VAST ad item', which distinguishes it from list operations like vast_list_ad_items and create/update/delete counterparts. It clearly conveys a retrieval-by-id operation.

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 alternatives such as vast_list_ad_items, vast42_get_ad, or draft_get_ad_item. There is no mention of prerequisites, exclusions, or preferred contexts.

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