ad_manager_google_get_ad_accounts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, which covers safety. The description adds no additional behavioral context (e.g., pagination, scoping, or what data is returned). It neither contradicts the annotations nor provides extra transparency beyond them.

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?

The description is a single short sentence, which is concise and front-loaded. However, it is too terse to add any usable nuance, so while it earns full marks for brevity, it lacks the substance that would make it well-structured.

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 the existence of numerous sibling tools with similar purposes, and no output schema, this description is insufficient. It does not clarify what the returned list contains, how account types map to parameters, or how this differs from related tools like ad_manager_google_get_ad_account_details. An agent would struggle to choose this tool 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?

Schema coverage is 100% – both 'type' and 'locationId' have descriptive text in the schema. The description itself adds nothing about parameters, but since the schema fully covers them, baseline 3 is appropriate.

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 action and resource: 'Get Google ad accounts' – a specific verb and object. However, it does nothing to distinguish itself from closely related siblings like ad_manager_google_get_ad_account_details or ad_manager_fb_get_ad_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?

There is no guidance on when to use this tool versus the many similar ad account retrieval tools. No context about account type selection, default behavior, or when to prefer this over get_ad_account_details. This is essentially a bare statement with no usage direction.

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