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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes one genuinely useful behavioral fact — that a successful read does not imply granted permission or verified restricted qualifications — but omits pagination, freshness, or failure modes.

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 short sentences, no filler, with the scope of returned data front-loaded. The phrasing is telegraphic and slightly cryptic ('base evidence', 'restricted qualifications'), which costs a point but nothing is wasted.

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?

An output schema exists so return values need not be explained, and annotations cover safety. What remains missing is the eligibility dimension implied by the tool name and any relation to sibling account-read tools, leaving an agent able to invoke it but unsure why it exists alongside google_ads_accounts_list.

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 50%: customer_id is documented as a 10-digit id, but connection_context has no description in either schema or tool description. The description adds no parameter semantics at all, so it neither compensates for the gap nor detracts. Baseline 3 applies.

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 concrete verb ('Read') and enumerates the resource fields returned: account status, currency, timezone, base evidence. That is well beyond a restatement of the name. However, it never addresses what 'eligibility' means in the tool name, nor distinguishes this from nearby reads like google_ads_accounts_list or setup_get_status.

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?

The second sentence ('Discovery does not grant permission; restricted qualifications remain unverified') is a caveat about interpreting results, not guidance on when to call this tool versus alternatives. With ~30 sibling read tools, the absence of any routing guidance or prerequisites is a real gap.

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