yd_ad_images_get

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

With no annotations, the description must fully disclose behavioral traits, but it only states the basic retrieval function. It omits details such as read-only nature, authorization needs (e.g., when client_login is required), rate limits, or response format. The minimal description does not add value beyond the obvious.

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 short sentence that is front-loaded with key information. It is concise without being verbose, though it could include more context without becoming overly long.

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 lack of output schema and annotations, the description is minimally adequate for a simple get tool. However, it does not elaborate on how the parameters interact (e.g., using 'associated' may require an ad context) or provide completeness for an agent to use it reliably in all scenarios.

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%, so the baseline is 3. The description adds minimal value by linking 'by IDs' to the 'ids' parameter and 'linked entities' to the 'associated' parameter, but this is implied. It does not clarify the meaning of 'linked entities' or provide additional context beyond 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 clearly states the verb 'Get' and resource 'ad images', and specifies two retrieval methods: by IDs or by linked entities. This effectively differentiates from sibling tools like yd_ad_images_add (add) and yd_ad_images_delete (delete).

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 over alternatives, or how to choose between the 'ids' and 'associated' parameters. The description lacks explanations of prerequisites or context for usage, making it insufficient for an agent to decide correctly.

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