Organizations post api key

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

Annotations declare readOnlyHint=false and destructiveHint=false, which is consistent with the description, but the description omits the most important behavioral fact for a key rotation: that generating a new key invalidates the previous one and breaks existing client_credentials integrations. It also says nothing about required admin/owner permissions or whether the key is returned once. With annotations carrying only a thin safety profile, this is a significant gap.

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?

A single short sentence with the operation front-loaded and no filler. It is efficiently written, though the brevity is partly under-specification rather than discipline.

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 mutation tool with four undocumented parameters, no output schema, and a near-duplicate sibling, one sentence is not enough to call it correctly or safely. An agent lacks the invalidation semantics, permission requirements, and payload expectations it needs.

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 description coverage is 0% and the four parameters (form, params, json_body, org_id) have no types, descriptions, or enums. The description only implies that an org is targeted ('the org's API key') and says nothing about what belongs in json_body/form or whether the key payload is supplied or generated server-side.

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?

States a specific verb+resource: generating/rotating an organization's API key, and adds the intended consumer (client_credentials / public API access). However, it does not distinguish itself from the nearly identical sibling vaultwarden_organizations_rotate_api_key (or vaultwarden_accounts_rotate_api_key), so an agent cannot tell which one to pick from the description alone.

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?

The parenthetical '(for client_credentials / public API access)' hints at the purpose of the resulting key but gives no when-to-use/when-not guidance and never mentions the obvious alternative, vaultwarden_organizations_rotate_api_key. Worse, the description claims to 'rotate', directly overlapping that sibling's name, leaving the choice to guesswork.

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