createTokenCreate a new API token for the current user by specifying name, scope, and expiration to enable authenticated access to Cloady resources.
Create a new API token for the current user
| Name | Required | Description | Default |
|---|---|---|---|
| requestBody | No | The JSON request body. |
Changes observed during successful MCP inspections.
v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose any side effects, such as the token being displayed only once or potential security implications. The annotations indicate destructiveHint=true, but the description provides no elaboration on what that means for the caller.
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 concise and to the point, with no unnecessary words. It effectively communicates the core purpose.
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?
The description is minimal, missing mention of potential returned data or any important caveats like token visibility. However, since there is no output schema, the absence of return value description is not a major issue.
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 only parameter, requestBody, has the generic description 'The JSON request body.' but the nested fields (name, scope, expires) lack descriptions. This leaves the meaning of scope and expires unclear, especially with enum values.
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 (API token) and specifies the scope (current user). It differentiates from sibling tools like revokeToken and listTokens.
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?
No guidance is provided on when to use this tool instead of listTokens or revokeToken. The description lacks any mention of prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.