list_ortb_native_image_assets

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

With no annotations, the description must fully disclose behavior, but it only states 'List all image assets'. It does not mention that pagination is required to truly list all (default limit 100, max 100), nor does it describe the return structure or ordering. The word 'all' is potentially misleading given the limit/offset parameters.

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 with no wasted words, front-loading the main action and resource. It is appropriately sized for a simple list tool, though it is slightly terse given the missing pagination behavior.

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 list operation with fully schema-documented parameters, the description provides the essential purpose. However, with no output schema and no annotations, it does not explain the return format, pagination semantics, or how 'all' relates to limit/offset, leaving some contextual gaps.

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 description coverage is 100% (template_id, limit, offset all documented). The description adds no additional parameter semantics beyond the template scoping, so the baseline of 3 applies since the schema already carries parameter meaning.

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 ('List') with a clear resource ('image assets') and scope ('for an ORTB native template'). It distinguishes itself from sibling tools like get_ortb_native_image_asset (single asset) and list_ortb_native_title_assets (different asset type).

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 context 'for an ORTB native template' implies this is the list operation scoped to a template, but it does not explicitly state when to use this over get_ortb_native_image_asset or mention pagination behavior with limit/offset. Usage guidance is implied rather than explicit.

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