marrow_create_key

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

No annotations are present, so the description carries the burden of behavioral disclosure. It does reveal the most important non-obvious behavior: the plaintext key is only returned once and must be copied. However, it does not mention other behavioral aspects like permissions, idempotency, or side effects beyond creation.

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 clean sentences, no filler. The purpose is stated first, followed by a critical one-time action warning. Every word earns its place.

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 5 parameters and no output schema, the description covers the essential non-obvious return behavior. It could benefit from a bit more context (e.g., typical usage or relationship between key_type and scopes), but the schema covers the parameters themselves, so the description is adequate for a creation tool.

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 description coverage is 100%, so all five parameters already have meaningful descriptions. The tool description adds no parameter-specific semantics, keeping the baseline of 3 as appropriate.

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') and the resource ('a new API key'), which is specific and distinguishes this from sibling tools like marrow_list_keys, marrow_revoke_key, and marrow_rotate_key. The wording is unambiguous and front-loaded.

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 for initial key creation, but it does not explicitly contrast with alternatives (e.g., rotate, revoke). The instruction 'copy it now' provides practical post-invocation guidance but no when-to-use or when-not-to-use guidance.

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