list_picklist

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

No annotations exist, so the description carries the full burden. It helpfully discloses the concrete endpoint pattern (picklists/picklist_<picklist>.php) and the shape of the return, and 'List' implies read-only, but it says nothing about auth requirements, pagination, caching, or error behavior for unknown picklist names.

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?

Purpose is front-loaded in the first line, followed by a tight Args block. The endpoint detail and return note are short and every sentence adds information; nothing is padded.

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?

An output schema exists so return values need not be fully spelled out, and the description still notes the extracted `items` list. Combined with the enumerated picklist values, an agent has enough to call it correctly, though guidance on unknown picklist names is missing.

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 description coverage is 0% with a single required string parameter, so the description must compensate, and it does: it enumerates the common picklist values ('accounts', 'contacts', 'products', 'vattypes', etc.). It still does not say whether arbitrary values are accepted or what happens on an invalid name.

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?

States a specific verb and resource ('List an Acumulus picklist') and clarifies the domain with 'reference data for dropdowns/validation'. It is clearly distinguishable from create_invoice and whoami, but it never contrasts itself with the generic acumulus_request sibling, which could also reach the same endpoint.

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?

Usage is only implied by the parenthetical about dropdowns/validation. There is no explicit statement of when to reach for this tool versus calling the underlying endpoint via acumulus_request, and no prerequisites or exclusions are given.

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