cortex_renew_user_key

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

Discloses the destructive side effect: 'invalidates the previous key,' which is crucial for an agent to understand the impact. No annotations provided, so the description carries the full burden. Could mention if the invalidation is immediate or affects active sessions.

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 concise sentences with no wasted words. Every sentence adds value: purpose, side effect, and authorization requirement.

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 simple tool with one parameter and no output schema, the description covers purpose, side effect, and prerequisite. Lacks details on response format or error conditions, but acceptable for its simplicity.

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 already describes 'userId' as 'The user login/ID to renew the key for' with 100% coverage. Description adds no further meaning beyond the schema, resulting in a baseline score of 3.

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?

Description clearly states 'Generate a new API key for a user' with the specific verb 'renew' and resource 'user key'. It explicitly notes that it invalidates the previous key, distinguishing it from retrieval tools like 'cortex_get_user_key'.

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?

States 'Requires superadmin API key,' providing a clear prerequisite. Does not explicitly exclude non-superadmin usage but implies it. No alternatives or when-not-to-use guidance given.

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