Account Register

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

It discloses that it requires human approval, creates state, returns masked credentials that are never logged, and that the session can be used by authz_compare.

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 well-structured, front-loading the approval requirement and then detailing parameters and behavior. It is concise and free of redundancy.

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?

It provides context about the tool's place in the authenticated toolchain, the approval mechanism, and the subsequent use of the session. It does not detail the output schema or error handling, but the essential information is present.

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?

It explains the meaning of signup_url, username_field, password_field, email_field, and name, and notes that credentials default to generated values. However, it omits descriptions for host and role.

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 that the tool creates a test account and registers the session, and it identifies itself as the one action in the toolchain that creates state, distinguishing it from siblings.

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?

It explains that it requires approval and is refused unless rules.allow_self_registration is set, and it contrasts with other actions that read state. However, it does not explicitly name alternative tools or conditions for when to use them instead.

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