Store or rotate a Bitwarden secret

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

Annotations declare idempotentHint=true and destructiveHint=true, and the description adds context: it states that the returned result omits the secret value, which is a behavioral trait beyond annotations. It also implies idempotent update when key matches, but doesn't detail what gets destroyed or authentication needs.

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 only two sentences, with no wasted words. It front-loads the critical operation (create/update) and concludes with a notable behavioral fact (omission of secret value).

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?

Given five parameters with zero schema descriptions, no output schema, and the tool being a mutation with destructive hint, the description is insufficient. It fails to explain the behavior of 'overwrite', what happens on key collision, how 'project_id' affects scoping, or error states. The omission note is helpful but not enough.

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 description adds no meaning to any of the five parameters. Required parameters 'key' and 'value' are unexplained, and optional parameters 'note', 'overwrite', and 'project_id' receive no guidance on semantics or constraints.

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 a stable secret or update the existing exact-key match in one project.' It specifies the verb (create/update) and the resource (secret), and implicitly distinguishes from sibling tools like get_secret or list_secrets by focusing on write operations.

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 description implies usage for both creation and exact-key update, but provides no explicit guidance on when to use store_secret versus alternatives like rotate or update through other means. No exclusions or context for when not to use this tool.

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