draft_get_catalog_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 burden. 'Get details' clearly implies a read-only operation, but the description does not disclose any additional behavioral traits such as error handling, permission requirements, or the meaning of 'draft' in this context. It is honest but minimal.

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, directly worded sentence with no filler or redundant information. It is appropriately sized for a simple getter.

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 one-parameter getter with no output schema, the description is mostly complete. However, it could explicitly distinguish this from the non-draft get_catalog_ad_item or list variants. The name carries much of the context, so the gap is minor.

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 schema describes the single parameter 'id' with 'Draft ad item ID' and has 100% coverage. The tool description adds no extra meaning beyond the schema, so the baseline score of 3 applies.

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 'Get' and identifies the resource as 'details of a specific draft catalog ad item'. This clearly distinguishes it from sibling tools like draft_list_catalog_ad_items, draft_create_catalog_ad_item, and the non-draft get_catalog_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 implies when to use this tool (when you need details of a single draft catalog ad item), but it does not explicitly state when not to use it or mention alternatives like get_catalog_ad_item for non-draft items. Usage is implied rather than guided.

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