import_key

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

No annotations provided, so the description carries full burden and does well: it discloses ECIES encryption, no plaintext transmission, and mutual exclusivity of mnemonic/privateKey. It stops short of stating auth requirements, persistence, or what the TEE does with the key after import.

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?

Three tight sentences, front-loaded with purpose and security property, ending with the mutually-exclusive parameter constraint. No filler.

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 5-param import tool with no output schema and no annotations, the description covers purpose, security behavior, and the key parameter constraint. It could still note authentication or where the imported key persists, but it is close to 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 schema already documents all five parameters including curve and chains defaults. The description reinforces the mnemonic/privateKey exclusivity and word-count constraint, but adds little beyond the schema on curve, chains, or keyType.

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?

States a specific verb (Import) and resource (key: mnemonic or private key) into a named system (Keygenix TEE). Clearly distinguishable from siblings like keygen (generate) and export_key.

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?

Implies usage context: bringing an existing key into the TEE rather than generating one. It doesn't explicitly name alternatives like keygen or describe when to prefer generation, but the import-vs-generate distinction is strongly implied.

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