Get billing metadata

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description adds nothing beyond that — no note on required admin/org scope, what metadata fields come back, or why it is openWorld.

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?

Four words with no waste and the resource is front-loaded, but brevity here is under-specification rather than efficiency — there is room to say more without bloat.

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 tool with an undocumented required org id, three undocumented optional pass-through params (form/params/json_body), no output schema, and an openWorld annotation needs far more guidance than one phrase. An agent cannot confidently construct a call from this.

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% across 4 parameters, so the description carries the whole burden and fails. Only the word "org" loosely implies _org_id is the organization identifier; form, params, and json_body remain entirely unexplained.

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?

It states a verb and resource ("Get org billing metadata"), so the basic operation is inferable. But it does nothing to distinguish this from near-identical siblings like vaultwarden_get_self_host_billing_metadata and vaultwarden_get_billing_warnings, leaving scope ambiguity.

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 indication of when this tool applies versus the self-host billing metadata variant or billing warnings tool. The agent must guess which billing endpoint matches its intent.

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