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

The description is consistent with annotations (readOnly, idempotent, non-destructive). It adds context by noting the connections are 'linked to this install', providing a scoping detail not present in annotations. No contradictions, and the read-only nature is clear from the verb 'List'.

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, clear, and concise sentence with no superfluous words. It efficiently conveys the core functionality without elaboration or redundancy.

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?

The description is adequate for a simple listing operation but lacks completeness: it does not explain what 'connections' entails, what the return format might be, or the role of the 'account' parameter. Given the absence of an output schema, the description leaves some ambiguity about the expected result, making it moderately complete.

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 schema includes a single parameter 'account' with no description, and the tool description does not mention it at all. With 0% parameter coverage, the description fails to clarify the purpose or meaning of the parameter, leaving users to guess whether it filters or specifies the account.

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 clearly states the function: listing OpenAI Billing admin API connections. It uses a specific verb ('List') and identifies the resource ('OpenAI Billing admin API connections'), distinguishing it from sibling tools like openai_billing_cost and openai_billing_usage.

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 description implies usage when one needs to see billing admin connections, but it does not explicitly state when to use it versus alternatives (e.g., openai_billing_cost or openai_billing_usage). It lacks any context about when not to use it or prerequisites, making the guidance implicit rather than explicit.

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