delete_ortb_native_template

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without indicating that deletion is permanent, whether there are cascading effects, or if special permissions are required. While the verb 'delete' implies a destructive action, no additional context is provided.

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, concise sentence of five words, front-loaded with the action verb. Every word is meaningful, and there is no redundant information or filler.

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 is simple (1 parameter, no output schema), and the description is minimally adequate. However, it does not differentiate this from the sibling delete_native_template, nor does it mention that deletion is irreversible or that IDs can be retrieved via list_ortb_native_templates. These are notable gaps for an agent selecting among similar delete tools.

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 input schema already documents the single `id` parameter with a clear description ('ORTB native template ID'), achieving 100% schema coverage. The tool description adds no extra parameter semantics, so it does not improve upon the schema, but the baseline of 3 is appropriate given the high schema coverage.

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 uses the specific verb 'Delete' and names the exact resource 'OpenRTB native template', clearly distinguishing it from sibling tools like delete_native_template or delete_zone_ortb_native_ad. It is unambiguous and immediately actionable.

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?

No explicit usage guidance is provided. The description implies that this tool is for deleting an OpenRTB native template, but it does not mention prerequisites, how to obtain the ID, or when to prefer this over the similar delete_native_template tool. This is a minimal viable level of guidance.

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