Connect to Ads Optimiser

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

Annotations already declare the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false), and the description adds genuinely useful behavior: this is a two-step device flow where the user approves in a browser and selects the workspace there. It omits details like code expiry or polling requirements, but it goes well beyond the structured fields.

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?

Two sentences with no filler, and the return value plus the required next step are both front-loaded. Every clause carries actionable information.

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?

There is no output schema, so the description must explain the return value, and it does (URL plus code, approved in browser). Combined with the explicit handoff to adsoptimiser_finish_connect, an agent has everything needed to run the flow correctly.

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 for the description to disambiguate. The description correctly implies no inputs are required to initiate the flow.

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?

States a specific verb and resource ('Start signing in to Ads Optimiser') plus the mechanism (OAuth device flow). It also specifies what the tool returns (a URL and code) and which sibling continues the flow, so it is distinguishable from adsoptimiser_finish_connect without opening either schema.

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?

Explicitly routes the agent to the follow-up call ('afterwards call adsoptimiser_finish_connect'), which is strong sequential guidance. It does not cover the edge cases of when not to start a flow, e.g. checking adsoptimiser_status first when already connected, so it falls short of full when/when-not coverage.

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