List Google Ads accounts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope context ('the signed-in user can access'), which tells the agent results are permission-scoped rather than exhaustive, but says nothing about pagination, result size, or handling of accounts with no access.

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 zero filler; the scope constraint comes first and the returned fields are enumerated compactly. Every clause earns its place.

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 output schema present, the description helpfully enumerates the returned fields, which is the key information an agent needs for a zero-param lister. It could go further by noting this is the prerequisite step for the ads_* report/query siblings, but nothing essential to calling it correctly is absent.

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 there is nothing for the description to clarify and the baseline of 4 applies. No parameter information is missing.

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?

Names the specific resource (Google Ads accounts) and enumerates the fields returned (ID, name, currency, manager/test flag), so the agent knows exactly what this yields. It is a noun phrase rather than a verb+resource statement, and it does not explicitly distinguish itself from the sibling adsense_list_accounts, so it falls short of a 5.

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 only implied: the tool takes no parameters and is clearly the discovery step for account IDs, but the description never says when to call it or points at siblings like ads_query that consume those IDs. Adequate for a zero-arg list tool, but no explicit when/when-not guidance.

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