draft_get_native_ad_item

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

No annotations are provided, so the description must carry the full burden of disclosing behavior, but it only restates the tool's purpose. It does not mention return format, errors, permissions, whether it is read-only (though 'get' implies it), or any draft-specific semantics.

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, front-loaded sentence that states the core action and object with no wasteful words. It is appropriately concise for a simple get-by-ID tool, though it sacrifices depth elsewhere.

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?

Given the lack of annotations and output schema, this description is too thin to fully inform an agent about the return value, draft vs. published implications, or how to distinguish this from the many sibling draft_* tools. It is minimally adequate for a fetch operation but leaves significant 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 coverage is 100% with a single 'id' parameter described as 'Draft ad item ID'. The description's 'specific' adds minimal interpretive value but does not add syntax, format, or context beyond what the schema already provides, matching the baseline.

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 'Get details of a specific draft native ad item' clearly states the verb (get), resource (draft native ad item), and scope (specific, implying by ID). It distinguishes from list operations and from non-draft get_native_ad_item by including 'draft', although it does not explicitly contrast with sibling draft_get_ad_item or draft_get_image_ad_item.

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 gives no guidance on when to use this tool versus alternatives such as draft_list_native_ad_items for listing or get_native_ad_item for published items. There are no prerequisites, exclusions, or context about draft vs. live behavior.

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