create_zone_ortb_native_ad

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a create (mutation) operation but does not disclose permissions, idempotency, whether a template is required, or what the response contains. This lack of detail makes it insufficient for a mutation 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, front-loaded declarative sentence with nine words. It conveys the essential purpose without redundancy or irrelevant details, earning every word's 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?

For a simple 3-parameter create tool with full schema coverage, the description is minimally adequate. However, it lacks behavioral details (e.g., return value, required template in practice) and usage guidance, which leaves gaps for agents unfamiliar with the domain. It is not as complete as the high-calibration example.

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%, with each parameter described ('ORTB native ad name', 'Standard zone ID', 'ORTB native template ID'). The description adds no additional meaning beyond restating 'standard zone' from the schema, so it stays at the baseline without enriching parameter understanding.

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'), the resource ('ORTB native ad'), and the scope ('for a standard zone'), distinguishing it from sibling tools like create_native_template or create_zone. The inclusion of 'standard zone' narrows the target and differentiates it from zone types like email or catalog zones.

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 offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing an ORTB native template), exclusions, or that other tools like update_zone_ortb_native_ad exist for modifications. The only implicit guidance is the 'standard zone' qualifier, but no explicit when/when-not instructions are provided.

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