Dv360.Line Item.Set Status

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

With zero annotations, the description carries the full burden for a mutation tool and does not meet it: it never states that archiving is effectively irreversible, what permissions are needed, or what 'guarded' actually enforces. The parenthetical '(guarded)' hints at a safety gate but leaves its meaning, trigger conditions, and failure mode undefined.

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?

A single front-loaded clause with zero filler; the action and the allowed values come first. It is arguably over-compressed rather than verbose, but nothing in it is wasted.

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?

An output schema exists so return values need not be described, but for a 4-parameter mutation tool with no annotations and 0% schema coverage, the description leaves the confirm/guard mechanic and ID semantics entirely undocumented. An agent could call it, but not confidently or safely.

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 0% across four parameters. The description does supply the missing value set for entity_status (activate/pause/archive), which is real added value, but advertiser_id, line_item_id, and especially the 'confirm' parameter are completely unexplained — the agent cannot tell that 'guarded' implies confirm is required for destructive transitions.

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?

States a specific verb and resource ('Set a line item's entityStatus') and enumerates the three target values, so the agent knows exactly what state transition is performed. It is distinguishable from dv360.line_item.update by name and by the status-only scope, though it never says so explicitly.

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 on when to call this versus dv360.line_item.update (which presumably edits other fields), nor on prerequisites such as whether the line item must be paused or a draft before archiving. The only usage signal is the word 'guarded', which is never explained.

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