listAdmobAdUnits

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

The description indicates a read-only list operation but does not disclose any behavioral traits such as authentication requirements, rate limits, or potential side effects. Since no annotations are provided, the description carries the full burden for transparency, but it is minimally adequate for a simple listing tool.

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 sentence with no extraneous information. It is concise and front-loaded with the key action and resource.

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 (list operation with 4 parameters) and the absence of an output schema, the description is somewhat complete but could be improved by mentioning the return format or pagination behavior. It meets the minimum threshold but has room for enhancement.

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%, so the parameters are already documented in the schema. The description does not add significant meaning beyond the schema; it only implies that publisherId is relevant. According to the guidelines, baseline is 3 when schema coverage is high, and the description does not warrant a higher score.

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 resource 'ad units' under an AdMob publisher account, which is specific and distinguishes it from sibling tools that list other resources like ad sources or apps. However, it does not emphasize the differentiation from siblings explicitly, so it's not a perfect 5.

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 like listAdmobAdSources or listAdmobApp. There is no mention of prerequisites, context, or exclusions. Usage is only implied by the action itself.

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