list_bills

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

Without annotations, the description carries the burden of behavioral disclosure. 'List' clearly indicates a read operation and 'Bigcapital list filters' hints at a passthrough behavior. But it doesn't disclose pagination, result shape, or defaults, leaving significant behavioral ambiguity.

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 single sentence is front-loaded with the verb and object and contains no filler. It is concise, though it is also sparse given the number of parameters and missing guidance.

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?

With 6 parameters, no output schema, no annotations, and a close sibling list_due_bills, the one-line description is insufficient. It doesn't explain filter semantics, return data, or how it differs from similar listing tools.

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 only 33% (sortBy and searchTerm have descriptions), and the tool description adds no parameter-specific meaning. The phrase 'Bigcapital list filters' is a generic umbrella rather than an explanation of filterRoles, viewSlug, customViewId, or sortOrder 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 uses a specific verb ('List') and resource ('vendor bills'), so the core function is clear. However, it doesn't differentiate this tool from the sibling list_due_bills or other listing tools, and 'Bigcapital list filters' is left undefined.

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?

There is no guidance about when to use list_bills versus list_due_bills, get_bill, or other list tools. The description merely restates the action implied by the name, with no exclusions, prerequisites, or alternative routing.

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