Connect an ad account

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

readOnlyHint=false signals this is not a plain read, yet the description frames it as 'Get a link', which could mislead an agent into treating it as a pure read. It adds the useful detail that the output is a link and names the platforms, but does not explain that this initiates an OAuth-style connect flow requiring user interaction, nor what the link represents. With annotations present the bar is lower, so a 3 is appropriate.

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?

A single, front-loaded sentence with no filler. The platform list is the only elaboration and it is directly relevant.

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?

For a 0-parameter tool with no output schema, the description covers what an agent needs to call it correctly and confirms the return is a link. It could be stronger by clarifying this is the entry point of the connect flow versus list_ad_accounts (which shows accounts already linked).

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?

The tool takes zero parameters, so the baseline is 4. There is nothing in the schema for the description to add or compensate for.

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 states a specific verb and resource ('Get a link to connect your own ad account') and names the supported platforms (Meta, Google, TikTok, X, ChatGPT Ads). It is clear what the tool does, but it does not differentiate itself from adjacent siblings like list_ad_accounts or inspect_ad_account.

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?

Usage is implied (use this when you want to connect an ad account) but there is no explicit when-to-use versus alternatives, no note about the relationship to list_ad_accounts/inspect_ad_account, and no prerequisites such as an existing auth session.

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