register

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

With no annotations, the description fully discloses key behaviors: creates an UNVERIFIED account, emails a one-time code, does NOT log in, and requires verification to get an API key. It also explains the one-time nature and credential reuse, providing rich behavioral context beyond the bare operation.

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 three well-structured sentences, front-loading the core purpose and then adding critical behavioral details. Every sentence adds value with no redundancy or wasted words.

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 description effectively captures the registration flow, including the unverified state, email verification, and API key acquisition. It lacks an explicit statement of the tool's return value, but given the absence of an output schema, the behavioral outcome (code emailed) is sufficiently conveyed.

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 0%, so the description must compensate. It explains the role of `email` and `password` as registration credentials, but completely omits the optional `display_name` parameter. This incomplete coverage leaves an agent without insight into an available input, though the schema's title/default provide some inference.

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 purpose with a specific verb ('Register') and resource ('a new HyperRoute account'), and distinguishes it from the sibling `verify` and `login` tools by explicitly noting it does NOT log in yet and requires a follow-up verification step.

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 gives clear usage context: this is the one-time registration step, and explicitly instructs to call `verify` next. It also indicates the login is saved for future sessions, implying registered users should not re-register. However, it doesn't explicitly name `login` as the alternative for existing users.

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