storyline_regenerate_line_item

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

No annotations exist, so description carries the burden. It discloses async behavior, typical duration (~1–3 min), return shape ({operationId, status}), and polling instructions. It does not mention whether the existing draft is overwritten or any permission requirements, but 're-generate' implies replacement.

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?

Three short sentences, front-loaded with 'Async' and the action. Each sentence adds value: operation, return/polling, timing. No waste.

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?

The description covers the async workflow, return contract, polling mechanism, and duration. There is no output schema and no annotations, so this description is sufficient for an agent to invoke and monitor the operation. Slight gap: no mention of prerequisites or failure behavior, but overall strong.

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%; each parameter has a clear description. The tool description adds no additional parameter semantics beyond the schema (e.g., no format details or constraints). Baseline 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 clearly states 'Re-generate a single line item's content draft' with a specific verb and resource. The word 'Async' adds a key behavioral scope. This distinguishes it from related tools like storyline_update_line_item or storyline_execute, though alternatives aren't named.

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 usage by indicating it is for regenerating a line item draft, but does not explicitly state when to use it versus alternatives such as storyline_update_line_item or storyline_execute. It provides helpful operational guidance (poll get_job, ~1–3 min), which partially compensates.

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