Log in to Reddit Ads

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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds genuine behavioral context beyond them: it opens a browser, blocks waiting for the callback, and returns the authorization URL on timeout. It stops short of describing credential persistence, timeout duration, or success behavior.

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 tight sentences, front-loaded with the core action and followed by the timeout fallback. No wasted words.

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?

With no parameters, no output schema, and annotations covering the safety profile, the description supplies the key missing context: the async browser/callback flow and the timeout return. It could note that authentication state affects subsequent sibling tools, but it is largely complete.

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 description has no parameter semantics to convey and the schema is fully trivial. Baseline 4 is appropriate for a no-param tool.

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 (open OAuth consent page) and resource (Reddit Ads login), making the purpose clear. It is easily distinguished from siblings by name, but it does not explicitly differentiate itself from reddit_ads_auth_status or reddit_ads_logout, relying on the reader to infer the relationship.

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 (authenticate before using other tools) but never stated. There is no explicit guidance on when to call this versus reddit_ads_auth_status, nor any prerequisite context. The only implicit cue is 'wait for the callback,' which the schema alone would not convey.

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