pbs_acme_account_list

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

The description discloses the read-only nature and the response schema (only name), which is sufficient for a simple list tool. However, it does not mention pagination or limits, though this is minor given the tool's simplicity.

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?

Two sentences with no wasted words; the key information is front-loaded (READ-ONLY, list names).

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 the tool's simplicity, the description covers the purpose, response format, and prerequisite. The output schema is not shown but the description states the response item, which is adequate.

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 coverage is 100% for the single parameter (proximo_target), and the description does not add meaning beyond the schema. The mention of PROXIMO_PBS_* config is context, not parameter semantics.

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 that the tool lists registered PBS ACME account names, specifies the response item structure ({"name": str}), and distinguishes it from pbs_acme_account_get for full detail.

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 notes it is READ-ONLY, directs users to pbs_acme_account_get for full account detail, and mentions the prerequisite PROXIMO_PBS_* config, providing clear when-to-use and alternatives.

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