gads_account_info

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

With no annotations, the description carries full burden but only states it gets info, lacking details on side effects, permissions, rate limits, or error conditions. While it is read-only by nature, more transparency (e.g., authentication requirements) would be beneficial.

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 concise sentence, front-loaded with the action and resource. Every word adds value, and there is no redundancy or unnecessary detail.

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 no output schema, the description helpfully lists the returned fields (name, currency, timezone, etc.). It lacks error handling or edge cases, but for a simple read-only tool, this is mostly adequate. Sibling context is provided but not leveraged.

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 input schema already describes the single optional parameter (customer_id) with a clear description. The tool description adds no further parameter meaning beyond listing returned fields. Schema coverage is 100%, so 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?

The description clearly states the verb 'Get' and the resource 'basic info for the current Google Ads account', listing specific fields (name, currency, timezone, manager flag, status). This distinguishes it from sibling tools like gads_list_accounts which likely list multiple accounts rather than the current one.

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 description implies usage for retrieving basic account info but provides no explicit guidance on when to use this tool versus alternatives (e.g., gads_list_accounts for multiple accounts, or other performance tools). No exclusions or alternative tools are mentioned.

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