register_agent

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It reveals the tool is non-functional and the reason: 'delegated agent-key registration is still scaffolding server-side and requires a wallet EIP-712 signature this server cannot produce.' This is complete transparency.

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 two sentences. The first sentence states the purpose, and the second provides the limitation. Every sentence is essential and well-structured, with no extraneous 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?

Given the tool is not yet available, the description provides all necessary context: what it would do, its current status, and why it cannot be used. No output schema or annotations are needed because the tool should not be invoked.

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 has 100% description coverage (each parameter has a brief description). The description adds no further details about the parameters beyond the schema, so the baseline of 3 is appropriate.

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: 'Register a delegated agent key so an AI agent can trade on a wallet's behalf without holding the wallet key.' The verb 'register' and the resource 'delegated agent key' are specific and distinguish it from sibling tools like place_order or get_balance.

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 warns that the tool is 'Not yet available' and explains why (scaffolding, requires EIP-712 signature). This tells the agent not to use it, which is a clear guideline. It lacks an alternative tool suggestion, but given no sibling serves this purpose, it is still helpful.

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