Send email login

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

The annotations already disclose that this is a non-read-only, non-destructive, open-world operation. The description adds useful behavioral context by saying it is pre-auth and device-scoped, but it does not cover rate limits, response behavior, or error conditions.

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 a single front-loaded sentence with no filler. It is efficient, though its extreme brevity leaves no room for supporting details an agent may need.

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 pre-auth, open-world email-sending tool with three undocumented parameters and no output schema, the description is too sparse. It identifies the core action and scope but omits parameter usage, expected response, and relevant operational constraints.

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 three parameters are named generically as 'form', 'params', and 'json_body' with no descriptions. The tool description provides no information about what belongs in each parameter, so it fails to compensate for the empty schema documentation.

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 verb ('Send') and resource ('2FA email code') plus the exact context ('during login (pre-auth, device-scoped)'). This distinguishes it from generic email-sending siblings such as vaultwarden_send_email or vaultwarden_post_email.

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 phrase 'during login (pre-auth, device-scoped)' gives a clear condition for use. It does not explicitly name alternatives or exclusions, but the context is strong enough for an agent to know when this tool applies.

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