Connect Ad Platform

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

Annotations already declare idempotentHint=true and destructiveHint=false, but description adds valuable context: returns stored connection object with UUID and status='active', and idempotent behavior on duplicate. No contradiction with annotations.

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?

Three sentences, each serving a distinct purpose: registration context, parameter summary, and idempotency behavior. No redundancy, efficient and front-loaded.

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, description sufficiently explains return (connection object with UUID and status). For a registration tool, this covers everything an agent needs to know: purpose, parameters, idempotency.

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 already has 100% description coverage with format details (Google 10 digits, Meta act_XXXXXXXXX) and constraints. Description adds meaning by explaining the 'name' as display label and the overall return object shape, but schema already covers semantics well.

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 tool registers a Google Ads or Meta Ads account in the AdOps workspace, with specific verb 'Register' and resource 'ad account'. It distinguishes from siblings by noting that subsequent tools (campaign_list, campaign_create, ads_report) can target it, and it specializes in connection setup.

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?

Description explains when to use (to register an ad platform for later use) and implies when not to (if already connected, it's idempotent). It explicitly names sibling tools that depend on this connection, providing clear context for selection.

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