Put policy vnext

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

Annotations already declare it is a non-read-only, non-destructive, open-world mutation. The description adds only 'newer response shape', which does not explain permissions required, what existing policy state is overwritten, or what the response actually contains. For a mutation with zero schema documentation, this is thin.

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 single sentence is front-loaded and free of padding, but it is under-specified rather than concise. Given the tool's complexity and five opaque parameters, far more information should have been packed into the opening lines.

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?

A mutation tool with five undocumented parameters, no output schema, and only annotation-level safety hints. The description does not compensate for the schema's 0% coverage, so an agent lacks the context needed to call this reliably.

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?

Five parameters with 0% schema description coverage and no explanation in the description. The phrase 'by type' loosely gestures at pol_type, but org_id, form, params, and json_body are entirely undocumented in both schema and description, leaving the agent unable to construct a correct call.

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?

States a verb ('update') and resource ('policy') and hints at a sibling distinction via 'newer response shape' versus vaultwarden_put_policy. However, it never clarifies what a 'policy type' is, what vnext implies functionally, or how it differs operationally from the older put_policy.

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?

No explicit when-to-use guidance or exclusions. The parenthetical 'newer response shape' weakly implies preferring this over vaultwarden_put_policy, but the agent must infer that. No prerequisites, policy type enumeration, or context about when a policy update is appropriate.

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