Get story details, versions, and media download links. Story status can be: pending, processing, paraphrasing, generating, generating_media, completed, failed.
| Name | Required | Description | Default |
|---|---|---|---|
| storyId | Yes | The story ID. Use list_stories to find it. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description lists possible statuses, which adds context about story lifecycle. However, lacks disclosure of side effects, authentication needs, or error conditions. For a read tool, this is acceptable but minimal.
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?
Two sentences: purpose then statuses. No redundant information. Front-loaded with main action. Highly efficient.
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?
For a simple 1-param retrieval tool with no output schema, the description covers purpose and statuses adequately. Could be improved by noting that output includes versions and media links.
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 coverage is 100% with a clear description for storyId. Description adds 'Use list_stories to find it' which provides helpful sourcing context. Baseline 3 appropriate.
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?
Clearly states the verb 'Get' and the resource 'story details, versions, and media download links'. Distinguishes from sibling tools like list_stories (lists stories) and create_story (creates).
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 explicit when to use vs alternatives. Mentions 'Use list_stories to find it' for parameter, but not tool selection. Could be improved by noting when to retrieve full details vs list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools have mostly distinct purposes. The only potential overlap is between create_story and quake_story, but quake_story is explicitly a 'do-over' with limitations, so confusion is minimal.
Most tools follow verb_noun pattern (e.g., create_story, get_balance), but 'login' and 'signup' are single verbs, and 'quake_story' uses an unconventional verb. This is a minor inconsistency.
With 10 tools covering account management, payments, story CRUD, and specialized operations (quake, remix), the count is well-scoped for the platform's purpose.
Covers core lifecycle (create, read, list, delete stories) plus payments and authentication. Missing update_story for editing metadata, but this is a minor gap.