Get self host billing metadata

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not explain the required _org_id scope, whether the call is org-admin-restricted, or what kind of billing metadata is returned.

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 single short phrase is efficient but is under-specified rather than concise. It does not front-load any useful scoping or usage information beyond repeating the tool title.

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?

There is no output schema, four undocumented parameters at 0% schema coverage, and an open-world read operation. Given this complexity and the description's single-phrase content, the definition is not complete enough for an agent to invoke it confidently.

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 the description mentions no parameters at all. With four parameters, including a required _org_id, the description fails to compensate for the schema's lack of documentation or clarify what form, params, and json_body are for.

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 'Get self-host billing metadata' is essentially a restatement of the tool name and title, adding no distinguishing detail. It does identify the resource and verb, but an agent cannot tell from this text alone how it differs from siblings like vaultwarden_get_billing_metadata or vaultwarden_get_billing_warnings.

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 guidance on when to use this tool, when not to, or which sibling to prefer. The description provides no context such as prerequisites, org-scoping rationale, or alternatives, leaving all usage decisions to inference from the name.

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