auth_signup

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states the action (register) but does not reveal important traits such as whether email verification is required, password constraints, rate limits, or what happens on duplicate emails. For a mutation tool, this is a significant gap.

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 a single concise sentence of eight words. It is front-loaded with the verb and contains no filler or redundant information.

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?

The tool is a registration mutation with no annotations and no output schema, yet the description only specifies the inputs. It does not explain the return value, error behavior, prerequisites, or post-signup flow. This leaves significant unknowns for an AI agent, making the description incomplete for effective invocation.

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 each parameter already has a basic description (e.g., 'User email address', 'User password', 'Additional signup options'). The tool description adds no further semantic value beyond restating 'email and password.' Baseline 3 is appropriate because the schema does the heavy lifting.

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's function: 'Register a new user with email and password.' The verb 'Register' is specific and the resource ('new user') is identified, distinguishing it from sibling auth tools like auth_login (authenticate) and auth_get_user (fetch user details).

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 the tool is for creating user accounts but does not explicitly state when to use it over alternatives or mention any exclusions (e.g., 'use auth_login after signup'). No alternatives are named, so guidance is minimal but the purpose is clear enough for basic selection.

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