Ldap import

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds 'bulk' and 'deprovision', but does not clarify whether deprovisioning disables or removes members (a meaningful distinction given destructiveHint=false), what existing data is overwritten, or what auth/directory setup is needed.

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 front-loaded sentence that wastes no words and leads with the operation and scope. It is efficient, though efficiency here comes partly at the cost of substance rather than by distilling rich content.

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 bulk mutation tool with three opaque parameters, no output schema, and no annotation-level detail on effects. The description leaves critical gaps: payload shape, idempotency, what is provisioned/deprovisioned, and result reporting, all of which an agent needs before invoking it.

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 all three parameters (form, params, json_body) are null-defaulted with no types or descriptions. The description says nothing to compensate, so the agent has no idea what to put in any of them or that all are apparently optional.

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 (bulk-provision/deprovision), the resource (org members + groups), and the source (external SCIM/LDAP directory). The purpose is clear, but it does not differentiate from similarly-scoped siblings like vaultwarden_post_org_import or vaultwarden_bulk_delete_member, so an agent must still infer which import path to use.

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 explicit when-to-use, no prerequisites (e.g. directory connector config, admin scope), and no named alternative among the many bulk_* siblings. The phrase 'from an external directory' implies context but leaves the agent to guess at selection criteria.

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