get_ortb_native_data_asset

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. 'Get details' clearly implies a read-only operation with no side effects, but it does not mention potential 404 errors, permission requirements, or response structure. This is adequate for a simple getter but lacks depth.

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 that directly states the tool's purpose without any fluff. It is appropriately sized for a simple getter and front-loads the key information.

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 2-parameter getter with no output schema, the description plus fully documented schema parameters provide sufficient context to understand the operation. However, it does not describe the return value details, which could be helpful but is not critical for a basic retrieval tool.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema; it says 'specific data asset' and 'ORTB native template' which broadly maps to the id and template_id parameters, but the schema already documents these as 'Data asset ID' and 'ORTB native template ID'. No extra context is provided.

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 (Get details), the resource (specific data asset), and the context (for an ORTB native template). It distinguishes from sibling tools like get_ortb_native_image_asset and get_ortb_native_title_asset by specifying 'data asset'.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that list_ortb_native_data_assets should be used for listing all data assets, or that this tool is for retrieving a single specific asset by ID. No exclusions or alternative tools are named.

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