Give the application an AI key

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

Adds substantial context beyond annotations: the secret is deliberately not returned, it lands in the app's environment, and a key with no funds is disabled until top-up. That is exactly the operational detail an agent needs to set user expectations after calling.

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?

Front-loaded with the action and the follow-up requirement; every sentence carries operational meaning. The parenthetical about hundreds of models and the API URL is slightly promotional but does clarify what the key unlocks.

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 single-parameter tool it covers the full lifecycle: create, save, redeploy, and the disabled-until-funded caveat. Nothing an agent needs to call it correctly or explain the result is missing.

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?

Only one parameter and the schema already documents it at 100% coverage ('A label for the key, like chatbot'). The description adds nothing further about naming conventions or constraints, so the baseline 3 applies.

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?

A specific verb+resource: creates an OpenRouter key and stores it as OPENROUTER_API_KEY in the application. It also disambiguates from generic env tools like set_env by naming the exact provider and env var, and from ai_wallet by describing the key rather than the wallet.

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 the required follow-up step ('Then `redeploy` so the running app picks it up'), naming the sibling tool. It doesn't cover when to prefer this over request_keys or ai_wallet, which keeps it short of a 5.

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