list_accounts

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the listing action and default account, with no mention of side effects, read-only nature, permissions, or response characteristics. The tool's behavior is largely transparent (non-destructive), but the description does not state this, so it fails to disclose anything beyond the basic action.

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, focused sentence that states the tool's purpose and additional relevant detail (default account). It is concise, well-structured, and every word contributes meaning without fluff.

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 tool's simplicity (no parameters, output schema exists), the description covers the basic purpose. However, it lacks behavioral context (e.g., read-only nature) and does not position the tool among its siblings, leaving some gaps in guidance for agents. It is minimally sufficient for a simple tool but not richly complete.

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?

With zero parameters, the schema already fully describes the input requirements. The description does not need to explain parameter semantics, and the baseline of 4 applies. The description does not add anything about parameters, but none are needed.

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 uses a specific verb ('List') and a clear resource ('all configured Google Ads accounts'), and adds unique information about the current default account. However, it does not explicitly differentiate from sibling tools like list_customers, though the term 'configured accounts' is somewhat distinct.

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 provides no guidance on when to use this tool versus alternatives such as list_customers or set_default_account. There is no mention of context, prerequisites, or exclusions, leaving the agent without information for tool selection.

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