pbs_acme_account_get

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

With no annotations, the description carries full burden. It declares read-only behavior, explicitly excludes eab_hmac_key with reason ('PBS never returns it on read'), and states configuration requirement. It could add details on error handling or response format, but overall it is transparent about key behaviors.

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 concise sentence that efficiently conveys purpose, scope, exclusions, and prerequisites, with no unnecessary words.

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 simple read tool with two parameters and an output schema, the description covers what is returned (account, directory, location, tos), a notable exclusion (eab_hmac_key), and a configuration prerequisite. It is nearly complete, lacking only potential error conditions.

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?

Both parameters are fully described in the schema (100% coverage). The description does not add additional semantics beyond the schema. It maintains baseline value without extra parameter detail.

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 explicitly states it is a READ-ONLY operation to get a single PBS ACME account's full config, listing included fields and explicitly noting what is excluded (eab_hmac_key). This clearly differentiates it from sibling tools like pbs_acme_account_create, delete, list, and update.

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 provides clear guidance on what the tool does and its scope ('get one PBS ACME account's full config'). It mentions a prerequisite (PROXIMO_PBS_* config). However, it does not explicitly state when to use versus alternatives or when not to use it.

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