google_ads_accounts_list

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

No annotations provided, so description carries full burden. Discloses read-only nature and return format. Could add details on authentication requirements or error states, but current level is adequate for a simple list operation.

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: first defines purpose and output; second provides usage context and parameter behavior. No wasted words, front-loaded with key 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?

Covers purpose, output, usage context, and parameter behavior. Lacks mention of pagination, filtering, or error handling, but given simplicity of the tool (one optional param, no nested outputs), it is nearly 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?

Schema covers customer_id (100%), but description adds value by explaining optionality, fallback to credential environment variables, and that omitting the parameter uses configured customer IDs. Lacks clarification on priority if both provided.

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 clearly states the tool lists all accessible Google Ads accounts, specifies the returned fields (id, descriptive_name, currency_code, time_zone, manager flag), and explicitly labels it read-only. It distinguishes itself from sibling tools by recommending use at session start.

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 instructs to use at the start of a session to choose a customer_id for subsequent calls. Mentions fallback behavior for other tools (GOOGLE_ADS_CUSTOMER_ID). Provides clear when-to-use context.

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