billing_get_account_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It simply restates that account info and billing details are returned. It does not explicitly state that this is a read-only operation with no side effects, nor does it mention any authentication/account context or rate limits. The header "Returns:" implies a read operation, but little else is disclosed.

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 short but redundant: "Get account information including billing details" and "Returns: Account information and billing details" say essentially the same thing. It is frontloaded but the extra sentence adds no value. It could be trimmed to a single sentence without losing information.

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?

With no parameters and an existing output schema, the description's load is small, but it still fails to provide the broader context that could resolve ambiguity among sibling billing tools. It doesn't say whose account is returned (e.g., current authenticated account), whether billing detail covers balance or history, or how this tool relates to other billing read tools. This is adequate for a trivial tool, but not fully self-contained.

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 tool has zero parameters and schema description coverage is 100%, so there are no parameter semantics to add. With 0 parameters, the baseline is 4. The description does not need to explain any input fields, and none are missing.

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 and resource: "Get account information including billing details." This clearly conveys what the tool does. The name already carries an explicit billing scope, so the purpose is distinct from unrelated siblings, though the description itself doesn't explicitly differentiate it from billing_get_current_balance or similar billing read tools.

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 about when to use this tool instead of the numerous sibling billing tools (e.g., billing_get_current_balance, billing_list_invoices, subaccount_get_balance_summary). No when-not-to-use conditions, alternatives, or selection criteria are mentioned, so an agent cannot confidently route between these related tools based on the description alone.

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