storyline_generate_brief

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

With no annotations, the description carries full burden. It discloses async behavior, the exact return shape ({ operationId, status }), the polling mechanism, and typical duration. This is rich behavioral context beyond what a schema could imply.

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 sentences with no wasted words. It front-loads the critical async nature, then purpose, then actionable steps. Every sentence earns its place.

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?

Despite lacking an output schema, the description explains the return value, polling, and follow-up workflow. Combined with complete param documentation and clear purpose, it gives the agent everything needed to invoke and handle this async tool correctly.

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% and both parameters are clearly documented ('Brand ID (defaults to active brand)' and 'Storyline ID'). The description does not add parameter-specific syntax but reinforces the storyline context. This aligns with the baseline 3 for high schema coverage.

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 opens with 'Generate the marketing brief for a storyline' and specifies contents (positioning, key messages, audience, timing, tone notes). This clearly distinguishes it from sibling tools like storyline_set_brief and storyline_generate_strategy by naming the exact artifact produced.

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?

Explicit workflow guidance is provided: poll get_job until completed, then review with storyline_get, and call storyline_confirm_brief to advance. It also gives a time estimate (~1–3 min) and clarifies that the operation is asynchronous, giving the agent clear when-to-use and how-to-proceed instructions.

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