Get dummy master password policy

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds the key behavioral detail that the result is an empty stub, so an agent knows it is not retrieving real policy data.

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 sentence that front-loads the action and result with no wasted words. It is appropriately sized for a simple dummy endpoint.

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 explains the dummy return value, but the three generic input parameters remain undocumented and there is no output schema. For an agent to invoke it confidently, it would need to know whether form, params, and json_body are ignored or required in some form.

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 schema has three parameters (form, params, json_body) with 0% description coverage, and the description does not explain them. It mentions a placeholder org id, but no such parameter appears in the schema, so it does not compensate for the undocumented inputs.

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 specific verb and resource: returns an empty master-password-policy stub. The words "dummy" and "placeholder" distinguish it from the real policy tool, though it does not explicitly name vaultwarden_get_master_password_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?

The phrase "for a placeholder org id" implies this is for dummy/placeholder scenarios, but it does not explicitly say when to use it instead of the real master-password-policy tool or what alternatives exist.

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