Post device token

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

Annotations already establish that this is a non-read-only, non-destructive, open-world mutation, so the description's job is to add context such as overwrite semantics for an existing token, required auth scope, or whether nulls clear the token. It adds none of that; 'Set/update' is the only behavioral signal, and it does not contradict the annotations.

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 phrase with no waste and the action front-loaded, but the brevity comes at the cost of under-specification rather than being tight-but-complete.

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 endpoint with an undocumented body wrapper, a required identifier, no output schema, and three sibling token endpoints, the agent needs overwrite semantics and payload placement. None are present, so the definition is not sufficient to invoke confidently.

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% across four parameters (device_id required, plus generic form/params/json_body), so the description carries the full burden. It only implies that a push token and a device are involved, without saying where the token goes (json_body?) or what device_id format is expected.

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 gives a concrete verb ('Set/update') and a concrete resource ('device push token'), so an agent knows exactly what effect to expect. It does not differentiate itself from the near-identical siblings vaultwarden_put_device_token, vaultwarden_post_clear_device_token, and vaultwarden_put_clear_device_token, leaving the POST-vs-PUT choice unexplained.

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?

There is no statement of when to use this tool rather than the PUT variant or the clear-token siblings, and no prerequisites (e.g., the device must already be registered). The only guidance is the verb itself.

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