account_overview

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

Discloses that archived objects are never returned, explains the derived 'serving' flag and 'serving_issues' for paused ancestors, adding significant behavioral context beyond the readOnlyHint annotation.

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 concise and front-loaded with the main purpose, though slightly technical. It could be a bit more streamlined but is efficient 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?

Given the single optional parameter, presence of output schema, and thorough explanation of behavior including edge cases like archived objects and serving_issues, the description is complete and well-rounded.

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 parameter 'include_paused' is not explicitly described, but the description implies its effect by mentioning 'shows active/paused objects only' and the default is true. Since schema coverage is 0%, more explicit parameter details would be ideal, but the context provided is helpful.

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 it provides a compact tree of campaign -> ad group -> ad with statuses and roll-up counts, and distinguishes itself from listing all ads by explaining the API limitation.

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?

Explicitly tells when to use ('Use this instead of trying to 'list all ads'') and provides context about archived objects not being returned, helping the agent decide between this and other tools.

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