accounts_list

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

With no annotations, description adequately conveys read-only behavior and details the return fields (id, org name, billing email, currency, status, active flag). No contradictions.

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 sentences efficiently cover purpose, prerequisites, output, and next steps with no 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?

Given no output schema and no annotations, the description is nearly complete for a parameterless list tool. It covers return fields, prerequisites, and workflow context. Lacks mention of error cases or pagination but is sufficient.

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?

No parameters, and schema description coverage is 100%. Baseline for zero parameters is 4, and the description adds value by noting the prerequisite login requirement, earning a 5.

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 tool lists billing accounts for the logged-in user, using specific verbs and resource naming, and distinguishes it from siblings like accounts_create and accounts_use by mentioning the workflow.

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?

Explicitly states prerequisite of prior login and suggests using accounts_use after listing. Provides clear context but does not explicitly state when not to use it beyond the implicit purpose.

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