tokportal_get_video_ad_code_request

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as false, so the safety profile is clear. The description adds valuable behavioral context beyond annotations by explaining that the `code` field remains null until the request reaches `in_review` or `finalized` status, which informs polling behavior.

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 consists of two concise, front-loaded sentences. Every sentence provides essential information: the core purpose and the critical detail about null behavior. No redundant or unnecessary text.

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?

Given the tool's simplicity (single parameter, no output schema), the description is nearly complete. It explains the polling nature and the null field behavior. It does not cover error conditions or rate limits, but for a straightforward read-only retrieval tool, this is adequate.

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?

Schema coverage is 100% with a single required `id` parameter described as 'Video ID.' The tool description does not add any additional semantics or constraints beyond what the schema already provides, so no extra value is added. Baseline 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 clearly states 'Get / poll the ad code for a video' and specifies it returns the latest ad code request. The verb 'get/poll' and resource 'ad code for a video' are precise, and the sibling tool `tokportal_create_video_ad_code_request` provides contrast, making the purpose unambiguous.

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 polling by mentioning that the `code` field is null until the manager submits or it is delivered, indicating repeated use to check status. While it does not explicitly list when not to use or alternative tools, the context of a single retrieval tool alongside a create tool makes the usage clear.

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