ghl_ad_google_account_get

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, so safety is clear. Description adds endpoint URL and OAuth scopes (adPublishing.readonly), which provides additional behavioral context beyond annotations. No contradictions.

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?

Description is short (two sentences plus endpoint info) and front-loaded. However, the first two sentences are slightly redundant ('Get ad account details' and 'Retrieve details...'). Still concise overall.

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 get-by-id tool, the description provides endpoint, OAuth scopes, and parameter context (via schema). No output schema, but return behavior is implied. Could mention what fields are returned, but not critical. Complete enough.

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% with descriptions for all three parameters. The tool description does not add any additional meaning or constraints beyond what is already in the input schema. 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?

Description clearly states 'Get ad account details' and 'Retrieve details of a specific Google Ads account'. Verb+resource is precise. Distinguishes from siblings like ghl_ad_google_account_list (list) and ghl_ad_google_account_delete (delete).

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?

Description implies usage through the verb 'get' and specifying 'specific', but does not explicitly state when to use this vs. list or other alternatives. No when-not-to-use guidance. Adequate but lacking explicit context.

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