View emergency access

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

The description adds real behavioral context beyond the annotations: the access is read-only over vault contents and is gated by an approval/wait period. That said, "(read-only)" sits in tension with readOnlyHint=false, which implies the call may mutate state (e.g. recording the access); the description does not explain that side effect, so the agent could be mildly misled about whether anything changes.

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 front-loaded sentence with zero filler: actor, action, scope and precondition all appear up front. It is arguably too terse for a 4-parameter tool, but nothing in it is wasted.

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?

With no output schema, no parameter documentation, and only partial annotation coverage, the description should carry more weight. It never explains what emer_id identifies, what the response contains (the grantor's ciphers?), or what happens if the wait period has not elapsed.

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 does not mention any parameter at all — not even the required emer_id, nor the opaque form/params/json_body wrappers. All four parameters must be inferred from the schema with no semantic help from the description.

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 states a specific actor, action and target: the grantee views the grantor's vault, read-only, as part of the emergency-access flow. This distinguishes it reasonably from siblings such as vaultwarden_get_emergency_access (metadata about the access record) and vaultwarden_takeover_emergency_access (account takeover), though it never names those alternatives explicitly.

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?

"After approval/wait elapses" gives one concrete precondition for legitimate use, which is genuine usage guidance. However, it never says when to prefer this over takeover_emergency_access or password_emergency_access, nor what to do if approval has not yet occurred.

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