Config

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

Annotations already declare readOnlyHint=false and openWorldHint=true, but the description does not explain why a seemingly read-oriented 'Return' operation is marked non-read-only, nor does it mention auth requirements, rate limits, or possible side effects. It adds only the startup-use context, leaving important behavioral traits unaddressed.

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 description is a single front-loaded sentence with no filler. Every phrase contributes to identifying the resource and the client-startup use case.

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 config retrieval tool, it gives a reasonable high-level indication of returned content (config, feature flags, environment URLs) and startup context. However, with no output schema and opaque optional parameters, it leaves the agent without enough detail about the response shape, auth needs, or how parameters affect the result.

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 input schema has three parameters (form, params, json_body) with 0% description coverage, and the tool description says nothing about what they are for or when they should be supplied. An agent gets no guidance on how to populate them or whether the tool can be called with no arguments despite all parameters being 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?

The description states a specific verb ('Return') and resource ('server config/feature-flags/environment URLs'), making the tool's scope clear. It does not explicitly name sibling tools such as vaultwarden_post_config or vaultwarden_get_diagnostics_config, but the read-oriented framing distinguishes it from delete/config mutation variants.

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 'used by clients on startup' implies the context in which this tool is appropriate, but there is no explicit when-to-use guidance, no exclusions, and no comparison to alternatives like vaultwarden_get_diagnostics_config or vaultwarden_get_settings_domains.

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