horizon_signup_anonymousCreates a new anonymous user account on horizOn with a display name, useful for guest logins or testing game/app backends without requiring credentials.
Creates a new anonymous user account on horizOn with a display name.
| Name | Required | Description | Default |
|---|---|---|---|
| displayName | Yes | Display name for the anonymous user (max 30 characters) |
Changes observed during successful MCP inspections.
v1.5.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It confirms a creation mutation but omits auth requirements, whether a session/token is created, whether existing anonymous accounts are affected, and any rate limits or side effects.
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?
A single front-loaded sentence with no wasted words. It is appropriately sized for a one-parameter tool and puts the action first.
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 mutation tool with no annotations and no output schema, the description does not explain session behavior, prerequisites, or how the result relates to subsequent sign-in calls. It is enough to identify the action but leaves important invocation context missing.
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 the schema already documents displayName and its max length. The description only restates the display-name parameter and adds no format or constraint details beyond the schema, making the 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?
States a specific verb and resource: creates a new anonymous user account. It also names the required display name, but does not explicitly differentiate from siblings such as horizon_signup_email or horizon_signin_anonymous beyond the tool name.
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 guidance is given on when to choose this tool over horizon_signup_email, horizon_signin_anonymous, or other auth tools. Prerequisites and conditions for use are absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.