yd_callouts_link

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as whether linking is additive or replaces existing links, error behavior for invalid callout_ids, authorization requirements, or idempotency. The mention of 'uses v501 API' hints at version but adds little behavioral context.

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: one sentence with 9 words. Every word contributes to the core purpose. However, it sacrifices completeness for brevity, earning a 4 rather than a 5 due to missing critical context.

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 no output schema, no annotations, and a large sibling list, the description is too incomplete. It does not explain return values, side effects, or how linking fits into the ad lifecycle. The agent lacks sufficient context to use the tool correctly without external knowledge.

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 descriptions for all three parameters. The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema already documents each parameter's purpose adequately.

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?

Description clearly states the action: 'Link callout extensions to an ad'. The verb 'link' distinguishes this from related siblings like yd_ad_extensions_add (which would create new extensions) and yd_ad_extensions_delete. The specific resource (callout extensions and ad) is 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?

No guidance on when to use this tool versus alternatives. The description does not explain prerequisites (e.g., callout extensions must exist) or contrast with yd_ad_extensions_add, which might be similar. The agent has no help deciding between linking and adding.

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