get_video_creative

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

No annotations are provided, so the description must carry the burden of disclosure. It only says 'Get details,' which implies a read operation, but it does not disclose any authentication requirements, rate limits, or what happens if the ID is invalid. It adds no behavioral context beyond the verb.

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 sentence that is direct and front-loaded. It contains no filler words and clearly conveys the action and target, earning its place.

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 one-parameter get tool, the description is minimal. However, with no output schema, it does not clarify what 'details' are returned or any special behavior. It is adequate but lacks richer context that could help an agent understand the full scope of the response.

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 already documents the only parameter 'id' as 'Creative ID' with 100% coverage. The description does not add any further meaning to the parameter, so it provides no additional value over the schema.

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 details of a specific video creative' uses a specific verb (Get), identifies the resource (video creative), and scopes it to a specific item (by ID). It clearly distinguishes from list, create, update, and delete operations, as well as from the generic get_creative or other creative types.

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 implies usage when you need details of one video creative by ID, but it does not explicitly state when to use this tool over alternatives like list_video_creatives or get_creative. No when-not or alternative guidance is provided.

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