list_vendors

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'List vendors using Bigcapital list filters' and does not mention response shape, pagination, permissions, whether omitted filters return all vendors, or any other operational behavior. 'List' implies read-only, but that is not explicitly stated.

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 sentence that immediately front-loads the verb and resource: 'List vendors.' It contains no filler or redundancy, and it is appropriately sized for a straightforward list operation.

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 annotations, no output schema, and a six-parameter input schema with only partial descriptions, a single generic sentence is far from complete. The agent cannot determine what filter values are valid, how multiple filters combine, or what the response will look like.

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 only 33%, and the description adds no parameter-level meaning beyond the generic phrase 'Bigcapital list filters.' Parameters like sortOrder, filterRoles, and customViewId remain undescribed in both the schema and the tool description, leaving the agent without enough context to use them correctly.

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 a specific verb and resource: 'List vendors' with the context of 'Bigcapital list filters.' This distinguishes it from read-one siblings like get_vendor and from other list tools like list_customers. It doesn't enumerate the filter capabilities, but the core purpose is unambiguous.

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 given on when to use this tool versus alternatives such as get_vendor for a single vendor or list_customers for customers instead of vendors. The only implied usage is 'when you need to list vendors,' with no conditions, exclusions, or hints about when a different sibling would be more appropriate.

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