Create a new FableMaker account. Returns a JWT token that expires in 26 days. Username must be at least 3 characters, password at least 7 characters with 1 digit.
| Name | Required | Description | Default |
|---|---|---|---|
| password | Yes | Password (min 7 chars, must contain at least 1 digit) | |
| username | Yes | Username (min 3 chars, must be unique) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses token expiration (26 days) and input constraints, but omits error behavior (e.g., duplicate username), side effects, or authentication requirements. Some context provided but incomplete.
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. Each sentence adds value: purpose, return value, input constraints. Well-structured for quick comprehension.
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 no output schema and no annotations, the description covers purpose, return value, and input constraints. However, it lacks error handling, rate limiting, and confirmation steps, leaving gaps for a signup tool.
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 descriptions for both parameters. The description repeats these constraints and adds token return info, but does not add significant meaning beyond the schema. 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 'Create a new FableMaker account,' specifying a concrete verb and resource. This distinguishes it from sibling tools like 'login' and 'create_story,' which serve different purposes.
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 for first-time account creation by saying 'Create a new account,' but does not explicitly guide when not to use it (e.g., for existing users) or contrast with sibling 'login.' No alternatives are named.
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.