admob_create_ad_unit

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

No annotations are provided, so the description must disclose behavioral traits. It mentions creation and supported formats but omits crucial details like authentication requirements (e.g., via `admob_auth`), side effects, or if the creation is immediate. This leaves the agent uninformed about necessary preconditions.

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 only two sentences, efficiently conveying the core purpose and format options without redundancy. Every word earns its place.

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?

No output schema is provided, so the description should explain return values (e.g., the created ad unit object). It does not. Additionally, with three required parameters, it doesn't mention that they are all required or the specific format for appId, though the schema covers this. The description is incomplete for a creation tool.

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?

The schema already provides descriptions for all three parameters (100% coverage). The description adds a list of supported formats that matches the enum, but does not add significant new meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 ('Create a new ad unit') and the resource ('AdMob account'), and lists supported formats, which distinguishes it from sibling tools like `admob_list_ad_units` and `admob_create_app`.

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 (need an existing app ID) but does not explicitly state when to use it versus alternatives, such as requiring an existing app from `admob_create_app` or listing apps first. No exclusions or prerequisites are mentioned.

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