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

readOnlyHint=true and openWorldHint=false already establish this as a safe, closed read, so the description only needs incremental value. It adds the return contents (balance, prices, top-up instructions), which matters because there is no output schema, but says nothing about permissions or freshness of the figures.

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 with the verb, resource, and payload listed in priority order. No filler, no repetition of the 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?

For a one-parameter read with readOnlyHint annotations and no output schema, the description covers what comes back and its scope. The only real gap is routing versus the sibling billing tools, which is a usage-guidance issue rather than a completeness one.

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 100% and the orgId property already explains it comes from org_list. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 and resource ('Returns the organization's shared wallet') and enumerates the payload (balance, prices, top-up guidance). It does not name the nearest siblings (billing_get, org_billing_transactions, org_billing_topup), so the 'shared wallet' scope is the only differentiator.

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 'organization's shared wallet' framing implies this is the org-level counterpart to the personal billing tools, but there is no explicit when-to-use statement, no exclusions, and no sibling named. Usage must be inferred from the scope adjective alone.

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