List AdMob accounts

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

The description essentially restates the resource and scope, adding no behavioral traits beyond what annotations already provide (readOnlyHint, idempotentHint, openWorldHint). It does not reveal any additional behaviors like rate limits or data freshness.

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?

A single, concise sentence that conveys the tool's purpose without any extraneous words. It is efficiently front-loaded.

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 absence of parameters, output schema, and complex behavior, the description is complete enough. It sufficiently informs an agent of the tool's output (listing accounts) and its scope (accounts available to the user).

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?

There are no parameters in the input schema, so the description does not need to add parameter-specific information. The schema coverage is 100% (vacuously), meeting the baseline for 0-parameter tools.

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 'List' and the specific resource 'Google AdMob publisher accounts', and the scope 'available to the authorized user'. It distinguishes this tool from siblings like 'admob_get_account' (which likely retrieves a specific account) by implying it returns all accounts.

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 when you need to see all available AdMob accounts, but it does not explicitly contrast with sibling tools. No guidance on when not to use it or alternatives is given.

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