List AdMob accounts

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

With readOnlyHint=true already provided, the description adds context about credential-dependent access ('accessible with the current credentials'), which is useful. However, it does not go further to describe pagination behavior, potential errors, or the structure of the returned account list. It adds some value but not extensive.

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 two sentences, front-loaded with the main action, and includes a practical tip. There is no redundancy or irrelevant information.

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?

The tool is a simple read-only list operation with schema documenting all parameters and an annotation confirming read-only behavior. The description covers the purpose and a common use case, making it complete enough for an agent to select and invoke the tool without further guidance.

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% for the two parameters (pageSize and pageToken), so the schema already explains their meaning. The description does not add any additional parameter-specific context, so the baseline score of 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 uses a specific verb ('Lists') and clearly identifies the resource ('AdMob publisher accounts') and scope ('accessible with the current credentials'). It also provides a concrete use case ('find your publisher ID'), which distinguishes it from siblings like list_apps or get_account.

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 gives clear context by stating the intended use ('Use this to find your publisher ID'), but it does not explicitly mention when not to use it or compare it to alternatives among the sibling tools. It lacks exclusions but provides enough situational clarity.

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