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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by enumerating the returned fields in the absence of an output schema, but says nothing about error behavior, missing connection, or permission scoping.

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?

One front-loaded sentence with no wasted clauses, and the returned-field list is packed efficiently. It's tight and readable, though it is so terse that it omits routing information a sibling-heavy toolset needs.

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?

For a simple single-param read with full schema coverage and safe annotations, the definition covers purpose and returned fields adequately. The only real gap is disambiguation from google_ads_list_accounts and google_ads_whoami in a crowded Google Ads sibling set.

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% and the single parameter documents digits/dashes tolerance and the 'defaults to your connected account' behavior. The description adds nothing about customer_id, so it rests at the baseline rather than earning above it.

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?

States a specific verb ('Get details') and resource ('your Google Ads account') and enumerates exactly what comes back (name, currency, timezone, manager/test flag). That said, it never distinguishes itself from close siblings such as google_ads_list_accounts or google_ads_whoami, so an agent can't tell from the text which of those to pick.

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: 'your Google Ads account' suggests the single connected account, and the field list implies 'use me when you need account metadata'. There is no explicit when-to-use, no exclusion of list_accounts/whoami, and no statement about prerequisites such as needing a completed Google Ads connection.

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