dai_skill

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

With no annotations, the description carries the full load. It discloses MODE (mixed read+write), AUTH (OAuth 2.0 required), CREDITS (read = 0 credits), and OUTPUT (Results for DAI entities). This gives agents essential behavioral info, though it could mention that some actions (e.g., delete) are destructive.

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 very concise and structured with clear MODE, AUTH, CREDITS, OUTPUT, and WHEN TO USE sections. Every sentence provides value with no redundancy. It is front-loaded with the key purpose.

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 (14 actions) and the absence of an output schema, the description covers purpose, behavior, auth, credits, and output type. However, it does not mention that additionalProperties: true allows dynamic parameters for specific actions, which could be important for agents to know.

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% (both parameters have descriptions in the schema). The description itself adds no further parameter details beyond what is already in the schema. Baseline 3 is appropriate as the schema already handles parameter semantics.

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 'DAI (Dynamic Ad Insertion) and broadcasting operations' and specifies 'managing Dynamic Ad Insertion auth keys and encoding profiles'. The enum values in the action parameter further detail the specific operations. This distinguishes it from sibling tools like line_items or orders, which handle different GAM domains.

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 'WHEN TO USE' section explicitly says 'Use for managing Dynamic Ad Insertion auth keys and encoding profiles', providing clear context. However, it does not specify when not to use it or mention alternative tools for non-DAI operations, which would be helpful given the large set of sibling tools.

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