list_ap_vendors

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states 'Fails loudly', indicating error handling behavior, but omits other important traits such as whether the operation is read-only, authentication requirements, rate limits, or pagination behavior (e.g., how page_size affects results).

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 very concise, consisting of two short phrases. While brevity is beneficial, it sacrifices essential information. The structure is straightforward but could be expanded with a sentence on parameters and typical use without becoming overly verbose.

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 that the tool has an output schema (unknown content), no annotations, and sibling tools exist, the description is insufficient for confident use. It lacks details on return values, filtering capabilities, or prerequisites. The 'Not in LCS /v1' note adds minimal context. A more complete description would cover what data is returned and any limitations.

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%, so the description must compensate by explaining parameters. However, it does not mention page or page_size at all. The agent cannot infer their semantics (e.g., page starts at 1, page_size controls number of results) from the description alone.

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 states 'List AP vendors', which clearly identifies the action and resource. The name itself distinguishes from sibling list tools (e.g., list_ap_bills, list_clients). However, it could be more specific about what AP vendors are (e.g., accounts payable vendor records) and the scope of the listing.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or scenarios where list_ap_vendors should be preferred over other list tools like list_ap_bills or list_clients. The '[Not in LCS /v1]' note is a version caveat, not usage guidance.

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