Get members

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the "users" synonym and says nothing about what is returned (member records with access level/status?), pagination, or permission requirements for this openWorld read.

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?

Five words, front-loaded with the verb and resource, with zero filler. Its brevity is efficient rather than padded, though it comes at the cost of substance.

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?

No output schema exists and four of five parameters are undocumented by both schema and description, so the agent cannot tell what the response contains or how to pass the envelope parameters. For a listing tool on a large org, missing pagination/return-shape information is a real gap.

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 coverage is 0% and there are 5 parameters, only org_id of which is required; the description never explains org_id's format nor what the data/form/params/json_body envelopes do. The word "organization" hints that org_id scopes the listing, but nothing compensates for the coverage gap.

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?

"List organization members" gives a specific verb and resource, and the parenthetical clarifies that members are users. It implicitly distinguishes itself from group-level siblings like vaultwarden_get_group_members, though it never states that scope contrast 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?

There is no when-to-use guidance, no prerequisites (e.g. admin privileges), and no reference to alternatives such as vaultwarden_get_users_json or vaultwarden_get_org_user_mini_details. The agent must infer everything from the name.

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