arcium_generate_keypair

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

The description highlights the critical behavioral trait that the private key is returned only once and must be stored securely, which is essential for correct and safe use. This compensates for the lack of annotations. No contradictory information is present, so annotation_contradiction is false.

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 extremely concise, consisting of two short sentences. The first sentence states the core function, and the second provides a critical warning. Every word earns its place with no 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 has no parameters and no output schema, the description adequately conveys the action and the one-time nature of the private key. However, it does not describe the format or structure of the returned keypair (e.g., likely an object with publicKey and privateKey), which would be helpful for the agent to parse the output.

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 tool has zero parameters, so the input schema is fully covered. The description adds value by specifying the cryptographic algorithm (x25519) and the critical warning about private key storage, which goes beyond what the empty schema provides.

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 generates an x25519 encryption keypair for Arcium. The verb 'generate' combined with the specific resource 'x25519 encryption keypair' leaves no ambiguity about its function. It is well-distinguished from sibling tools which focus on computations, encryption/decryption, and querying network state.

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 tool is a prerequisite for encryption operations, as it generates the keypair needed. However, it does not explicitly state when to use it vs. alternatives (e.g., importing an existing key). The warning about storing the private key securely provides some context, but there is no explicit guidance on when not to use this tool.

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