ebay_create_signing_key

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

With no annotations provided, the description carries full burden. It discloses that eBay does not store the private key, which is crucial. However, it lacks details on idempotency, rate limits, or what happens on duplicate requests, leaving some behavioral ambiguity.

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, each carrying significant information: the purpose and cipher options in the first, the critical warning in the second. No unnecessary 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?

For a creation tool with no output schema, the description tells the key action and warning but doesn't detail the response format (e.g., what keys are returned). While the warning implies the private key is returned, the public key or key ID is not mentioned, leaving some incompleteness.

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% with the single parameter 'signingKeyCipher' described as 'Cipher for the generated keypair, e.g. ED25519 or RSA'. The description does not add extra meaning beyond this schema information, meeting the baseline.

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 action (create), the resource (signing keypair), and its purpose (API digital signatures). It distinguishes from sibling tools like ebay_get_signing_key by being the creation counterpart.

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 includes an explicit warning to save the private key immediately, implying when to use the tool and a critical post-use action. However, it does not specify when to prefer this tool over alternatives or mention any prerequisites.

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