wais_register

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

With no annotations provided, the description carries the full burden. It discloses the use of SD-JWT selective disclosure, the sharing of only required claims, and the optional claims parameter behavior. It lacks details on error scenarios or potential side effects, but the behavioral traits are sufficiently transparent for a registration tool.

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 concise, at roughly 8 lines, with a clear structure: introduction, behavioral note, prerequisite, and parameter explanations. Every sentence adds value without 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?

Given the tool's simplicity (2 parameters, no enums, no nested objects) and the presence of an output schema, the description covers all necessary aspects: purpose, usage order (wais_discover first), parameter semantics, and default behavior. It is complete for the intended use.

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 site_url as 'The site.url from agents.json' and claims as 'Claims to disclose (e.g. ["email"]). If not provided, uses required_claims from agents.json automatically.' This adds meaningful context beyond the bare schema titles.

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 'Register the user at a WAIS-compatible site using their WAIS identity' with specific verb and resource. It distinguishes from sibling tools like wais_discover by explaining the registration action and the use of SD-JWT selective disclosure.

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 explicitly advises 'Call wais_discover first to see what claims the site needs,' providing a clear prerequisite. It also explains the default behavior when claims are omitted, offering good context for when to use the tool versus relying on defaults.

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