ebay_create_signing_key

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

Discloses the key types and the irreversible loss of private key if unsaved, but does not describe the response structure or authentication requirements. With no annotations, the description carries full burden and is partially adequate.

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?

Two sentences: first establishes purpose and options, second delivers critical warning. No unnecessary text, perfectly front-loaded.

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?

Adequately covers a simple create tool with one parameter. Lacks explicit mention of return value (e.g., public key, key ID), but the warning partially compensates. No output schema, so description could be richer.

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 has 100% coverage with enum descriptions. The description reiterates cipher options and recommendation, adding negligible value beyond schema.

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 states 'Create a new signing keypair for API digital signatures' with specific verb+resource, clearly distinguishing from sibling tools like ebay_get_signing_key (retrieval) and ebay_get_signing_keys (listing).

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?

Explicit warning to save private key immediately provides critical usage guidance. However, no direct comparison to alternative creation methods or exclusions, though the name implies one-time creation.

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