get_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. The verb 'Get' strongly implies a read-only operation, and no side effects are mentioned, which is a safe profile. However, the description does not explicitly confirm read-only behavior, error handling, or any edge cases. It is minimally transparent but not misleading.

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 10 words. It is front-loaded with the action verb and resource, with zero wasted words. Every word contributes to the purpose.

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 with two fully documented parameters, but there is no output schema. The description says 'details' without specifying what those details include, which could leave the agent uncertain about the response. For a simple getter, this is adequate but could be richer with a brief mention of return content. The lack of annotations and output schema makes the description the only source of context beyond the request schema.

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 covers 100% of the parameters with descriptions ('ORTB native ad ID' and 'Standard zone ID'). The description does not add additional meaning beyond the schema, which is acceptable given the high schema coverage. The terms 'specific ORTB native ad' and 'standard zone' loosely map to the parameters but add no new semantics.

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 a specific verb ('Get') with a clear resource ('details of a specific ORTB native ad') and context ('for a standard zone'). This unambiguously distinguishes the tool from sibling list/create/update/delete operations on the same resource.

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 the tool is for retrieving a single ad by ID within a specific zone, but it does not explicitly state when to use this versus alternatives like list_zone_ortb_native_ads, nor does it mention exclusions or prerequisites. The context is clear from the wording but no direct comparison is given.

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