preview_story

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the tool 'builds' a URL, but does not disclose whether it validates story existence, whether it returns a relative or absolute URL, whether it requires a running Storybook server, or what the output format is. More detail is needed.

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 one sentence with no waste, and it front-loads the core purpose ('Build a Storybook iframe preview URL') before mentioning optional parameters. It is efficient and easy to parse.

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?

This tool has 4 parameters with nested objects, no output schema, and no annotations. The description does not explain how the returned URL is used, how to obtain a valid storyId (e.g., from list_stories or search_stories), or any limitations. For an agent to call it correctly, more context is needed.

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%, so the description must compensate for parameter understanding. It mentions 'optional args, globals, and viewport' but does not explain what these are in the Storybook context, how they affect the URL, or the format beyond the schema's structural definition. The description adds minimal value over the raw schema.

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 states a specific action ('Build') on a specific resource ('Storybook iframe preview URL'), and uniquely identifies this tool among siblings, all of which are data-fetching or analysis tools. It distinguishes by being the only URL builder.

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: when you need a preview URL for a story. However, it does not explicitly state when to prefer this over other tools, nor does it mention any exclusions (e.g., 'use this instead of get_story for rendering'). The context is clear but no explicit guidance is given.

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