yd_ads_add_dynamic

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

No annotations are present, so the description carries the full burden. It only states 'create' but discloses nothing about required permissions, side effects, error conditions, or the nature of dynamic ads. For a mutation tool, this is a significant gap.

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 extremely concise with a single sentence containing no filler. However, the brevity sacrifices essential detail, making it less useful overall. It is efficient but insufficiently informative.

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 complexity (creating a dynamic text ad with multiple optional parameters), no output schema, and no annotations, the description is inadequate. It does not help the agent understand what dynamic ads are, how they differ, or what the parameters do. The context is incomplete.

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 60% (3 of 5 parameters described). The description adds no parameter information beyond what the schema already provides. Parameters ad_image_hash and sitelink_set_id lack descriptions, and the tool description does not explain their role. It fails to compensate for the missing schema documentation.

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 'Create a dynamic text ad.' clearly states the verb and resource, distinguishing it from other ad types by name. However, it does not explain what makes a dynamic text ad different from regular text ads, and there is a sibling yd_ads_add which could be for standard text ads, so the differentiation is implied but not explicit.

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 like yd_ads_add, yd_ads_add_image, or yd_ads_add_shopping. The agent must infer the appropriate context from the tool name alone, which is insufficient.

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