Activate a prepared delegation by supplying the owner's signature over its enable digest. Auth required.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | delegation id (uuid) | |
| owner | No | optional owner address, when it differs from the caller | |
| enable_sig | Yes | owner's 65-byte signature over the digest, 0x… |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Auth required' and implies a state change, but it omits side effects, reversibility, whether the prepared state is consumed, and failure/response behavior. This is a thin behavioral disclosure for a mutating 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 a single front-loaded sentence with no filler. Every word contributes: the action, the target state, the required signature, and the auth requirement.
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 state-changing tool with no annotations and no output schema, the description covers the core action and auth requirement but leaves out explicit prerequisite details (that the delegation must already be in prepared state) and postconditions. It is minimally viable but not fully complete.
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 100%, so the baseline is 3. The description adds some useful context by calling the digest the 'enable digest' and emphasizing the 'prepared delegation' state, but it does not materially clarify id, owner, or enable_sig beyond what the schema already documents.
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?
Description uses a specific verb ('Activate') with a clear resource ('prepared delegation') and a precise mechanism ('owner's signature over its enable digest'). This clearly distinguishes it from sibling tools like prepare_delegation, renew_delegation, and revoke_delegation.
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 phrase 'prepared delegation' clearly implies this is used after prepare_delegation, and the requirement of the owner's signature gives concrete usage context. It does not explicitly name alternatives or exclusions, so it stops short of the top score.
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 resource and action. Within the prediction market domain, prepare vs create vs submit are clearly differentiated by signing model (client-signed vs server-signed). Even similar-sounding tools like check_spend and check_pm_order are unambiguously scoped to general spending vs PM orders, and their descriptions reinforce the boundary.
All 47 tools follow a consistent verb_noun pattern with lowercase snake_case. Verbs like get, list, create, cancel, revoke, prepare, submit, set, remove, and poll are used uniformly. There is no mixing of styles or vague verbs like 'process' or 'run', making the surface highly predictable.
47 tools is significantly above the 25-tool threshold for 'too many'. While the server covers a broad and complex domain (prediction markets, policy, delegations), the sheer count makes the surface heavy and potentially overwhelming. Some consolidation (e.g., merging related PM order operations) could reduce cognitive load without sacrificing functionality.
The tool set provides comprehensive lifecycle coverage across all major subdomains: authentication, policy versioning, delegation CRUD (prepare/confirm/list/get/revoke/renew), intent management, PM order flow (create/cancel/list/prepare/submit/check), credential management (store/list/revoke), balance and top-up operations, and account-level actions (export, offboard, panic). Minor omissions exist (e.g., no dedicated tool to view a single credential in detail or update an intent), but agents can work around these with existing tools.