create_api_key

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It critically warns that the secret is returned only once, which is a key behavioral trait. Adding details about key limits or replacement would strengthen it further, but current detail is strong.

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 consists of three concise sentences, each serving a clear purpose: stating the action, highlighting a critical warning, and specifying authentication requirements. No unnecessary words or redundancies.

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 tool with zero parameters and no output schema, the description covers the essential aspects: purpose, critical behavior (secret shown once), and authentication requirement. It could mention the HMAC type more explicitly or describe the key's usage, but overall it is sufficiently 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?

The input schema has no parameters and 100% coverage, so the baseline is 3. The description adds value by explaining the behavior and authentication context, which compensates for the lack of parameters and justifies a higher score.

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 'Create a new HMAC API key for the authenticated wallet', which is a specific verb and resource. It distinguishes itself from sibling tools like 'delete_api_key' and 'list_api_keys' by focusing solely on creation.

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 mentions the prerequisite of a session token from 'login' but does not explicitly state when to use this tool versus alternatives like deleting or listing keys. However, the context of creation is clear, and siblings serve different purposes, providing implicit guidance.

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