list_ortb_native_data_assets

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 implies a read-only operation via 'List', but it does not explicitly confirm safety, does not explain pagination behavior despite limit/offset parameters, and does not mention any constraints or return characteristics.

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 sentence that states the tool's purpose directly with no filler. It is appropriately sized for the simplicity of the operation and front-loads the key action and resource.

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?

Without annotations or an output schema, the description leaves the agent without information about the return format, pagination behavior, or how data assets differ from closely related asset types. This is a significant gap for a list tool, especially given the existence of similar list tools for images and titles.

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 provides 100% description coverage for all parameters, including 'template_id', 'limit', and 'offset'. The description adds no additional semantic meaning beyond the schema; it merely restates the template context already present in the schema.

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 'List' and names the resource 'data assets' scoped to 'ORTB native template'. This clearly distinguishes it from sibling tools like list_ortb_native_image_assets and list_ortb_native_title_assets, which handle different asset types.

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 guidance is provided on when to use this tool versus alternatives such as get_ortb_native_data_asset for retrieving a single asset or list_ortb_native_image_assets for image assets. The description only states what the tool does, not when to select it.

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