get_password

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

The readOnlyHint annotation already signals no modification, and the description reinforces sensitivity by warning about exposing credentials. While it does not explicitly state 'read-only' in prose, the annotation covers that aspect, and the warning about misuse adds useful behavioral context beyond the annotation.

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 concise, using two sentences to convey purpose, usage constraints, and a pointer to related tools. There is no redundant wording or unnecessary detail.

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?

The description covers what the tool returns (plaintext secret, notes, custom fields), when to use it (specific id from user), and how to obtain valid ids. Combined with readOnlyHint and openWorldHint annotations, it provides enough context for an agent to invoke it correctly without additional information.

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?

The single parameter 'id' is clearly described as the password id to reveal, matching the schema description exactly. No further detail is provided (e.g., expected format or source), but the explanation is sufficient for correct usage given the tool's narrow scope.

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 tool's purpose: to reveal a single password entry by its id, including plaintext secret, notes, and custom fields. It also distinguishes itself from list_passwords and search_passwords by explicitly noting that ids come from those tools.

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 provides explicit usage guidance: only call it for a specific id the user has asked to see, and never for bulk export. It also directs callers to obtain ids via list_passwords or search_passwords, reducing ambiguity about when 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.