regenerate_api_key

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

No annotations provided, but description discloses destructive effect (invalidates key, blocks access) and confirmation requirement. Doesn't mention return value, but adequate given mutation.

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 covers purpose and effect, second gives usage guideline. No fluff, 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?

Covers purpose, effect, usage warning, and confirmation. Lacks output format but mutation tools often return simple success. Adequate for a dangerous action.

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 100% with two boolean parameters. Description adds only that confirm=true executes the action, mostly redundant with schema descriptions. Baseline 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 it regenerates the API key, invalidates the current one, and blocks access. Distinguishes from sibling tools like get_api_key (read) and regenerate_plugin_token (different token).

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?

Explicitly states 'Usar solo si el usuario lo pide explicitamente' (use only if user explicitly asks) and notes it's a mutation requiring confirmation. No explicit alternatives but context is clear.

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