Register an Ed25519 public key. Returns an api_key shown once. payload must be a JSON string you signed.
| Name | Required | Description | Default |
|---|---|---|---|
| payload | Yes | JSON string: {"name":"…","issued_at":"RFC3339"} — exact signed bytes. | |
| signature | Yes | Ed25519 signature of payload. | |
| public_key | Yes | 32-byte Ed25519 public key, hex or base64. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It usefully discloses that the api_key is shown once and that payload must be a signed JSON string, but it does not describe side effects, irreversibility, auth requirements, or behavior on repeated registration with the same key.
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?
Two short sentences with no filler; the key behavioral constraint and return caveat are front-loaded. Every sentence earns its place.
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 simple three-parameter registration call without an output schema, the description states the important return behavior and the signing reqirement. It could add a note about what the api_key is used for, but the core call is adequely specified.
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?
The input schema already documents all three parameters with 100% coverage, including that payload is the exact signed bytes. The description adds little beyond the schema, mainly restating that payload must be signed.
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 states a clear verb and resource: registering an Ed25519 public key, and notes the api_key return. It does not explicitly connect the key to the 'publisher' concept implied by the tool name, but the operation is distinct from the sibling app CRUD tools.
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 this is an onboarding/registration step, but it never states when to use register_publisher instead of publish_app or search_apps, nor does it mention any prerequisite relationship. No alternatives or exclusions are provided, though the purpose is reasonably inferred from the name and siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation: publisher registration, app creation, retrieval by ID, directory search, update, and delete. There is no meaningful overlap between these actions, and their purposes are clear from the names alone.
All tool names follow a consistent verb_noun pattern: register_publisher, publish_app, get_app, search_apps, update_app, delete_app. The naming is uniform, predictable, and easy for an agent to pattern-match.
Six tools is a well-scoped size for a directory server. Each tool covers an essential part of the app listing lifecycle without unnecessary duplication or bloat.
The surface covers the full lifecycle: publisher onboarding, create, read by ID, search, update, and delete. The signing and API key flow is also represented, leaving no obvious dead ends for the stated directory purpose.