create_scrollytelling_story

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

No annotations are provided, so the description carries full burden. It describes the output pattern (text left, charts right) and mentions parameter defaults, but it does not disclose behaviors like file overwriting, validation of steps, required permissions, or error handling. The presence of an output schema (indicated in context) is not mentioned, and step structure is left 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?

The description is two sentences, each adding value: the first states the core action, the second provides a concrete pattern reference. No redundant words; it is efficiently scoped.

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 tool creates a multi-section interactive story, the description covers the basic layout and parameters. However, it lacks details about the step structure (required nested keys), expected behavior with empty steps, and output handling. With an output schema present, some burden is relieved, but step semantics remain underspecified.

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%, so baseline is 3. The description does not add significant meaning beyond what param descriptions provide—it repeats the purpose but doesn't clarify the structure of 'steps' or usage of other params. The step object is left as 'additionalProperties: true' with no extra guidance.

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 the tool creates a 'scroll-driven HTML data story (scrollytelling)' with a specific pattern (text left, charts right). It uses a specific verb 'create' and resource, and the title and description distinguish it from sibling tools like create_chart or build_dashboard.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. It only describes what it does, leaving the agent to infer usage context without explicit direction.

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