List mediation groups

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

Annotations already mark the tool as read-only and open-world. The description adds behavioral context by detailing the EBNF filter expression and the fields supported (DISPLAY_NAME, STATE, PLATFORM, FORMAT), which helps the agent understand filtering behavior.

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 a parenthetical, front-loaded with the main action. It is concise without wasting words, though it could be more structured to highlight the filter feature.

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 five parameters and no output schema, the description explains the listing action and filter but omits pagination details and parameter use cases. It is minimally complete but leaves gaps.

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 only 40% schema description coverage, the description adds some meaning for the 'filter' parameter (EBNF expression and fields) but does not clarify 'all', 'pageSize', 'pageToken', or 'publisherId' beyond what minimal schema descriptions exist.

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 action ('List') and the resource ('mediation groups under an AdMob account'). It differentiates from sibling tools like 'admob_create_mediation_group' by focusing on listing, and adds specificity with the optional EBNF filter expression and allowable fields.

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 this tool is for listing mediation groups, not creating or updating, but lacks explicit guidance on when to use this versus other list tools (e.g., list_ad_units). There is no mention of alternatives or when not to use it.

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