tokens-create

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

Discloses that the token is returned only once and cannot be retrieved again, which is critical behavioral information. No annotations are provided, so description carries full burden.

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 straightforward sentences with no wasted words. The action and crucial note are 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?

Completely covers the tool's purpose, return value, and critical behavioral note. For a simple one-parameter tool, no gaps remain.

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% and description adds a concrete example ('Claude Code laptop') for the 'name' parameter, enhancing clarity beyond the schema definition.

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?

Clearly states verb 'creates' and resource 'API token' for 'current user'. The description effectively distinguishes from sibling tools like tokens-delete and tokens-list by specifying the creation action.

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?

Provides explicit warning to save the token as it cannot be retrieved again, which is a key usage guideline. However, does not explicitly state when to use this tool over other token-related tools, though there is only one creation tool.

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