Create mediation group

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

Annotations only provide readOnlyHint=false, so the description carries the burden for behavioral disclosure. It adds the required admob.monetization scope and clarifies the purpose. It doesn't describe failure modes or return value, but for a create tool with a write annotation, it is adequate.

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?

Two sentences with no redundancy. The first sentence is action-oriented and information-rich; the second covers the auth requirement. Well-structured and easy to parse.

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 has 8 parameters and no output schema, but the schema is rich and the description provides a high-level overview plus auth requirement. It lacks an explicit description of return value or typical use-case boundaries, but is complete enough for an agent to invoke correctly with schema support.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no significant parameter meaning beyond mentioning 'optional mediation lines,' which maps to mediationGroupLines already described in the schema. Baseline 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 clearly states the action ('Creates'), the resource ('mediation group'), and key attributes (format/platform, ad units, optional mediation lines). It distinguishes from sibling tools like list_mediation_groups and update_mediation_group by explicitly indicating creation.

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 clear context on what the tool does and the required scope, but it does not explicitly state when to use it over alternatives or mention exclusions. Since sibling tools include update_mediation_group, the create context is implied but not explicitly contrasted.

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