list_customers

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only says 'List customers' and offers no information about pagination, result limits, default sorting, or whether any side effects occur. This is minimally transparent for a list operation.

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 with no filler and the main verb and resource are front-loaded. It is appropriately concise for a simple list tool, even though the filter phrase is somewhat generic.

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, and no annotations, this description is not complete enough for reliable invocation. It omits pagination behavior, filter semantics, default ordering, and return shape, leaving the agent dependent on parameter names and external Bigcapital knowledge.

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?

The input schema describes only sortBy and searchTerm, covering 2 of 6 parameters (~33%). The tool description does not explain viewSlug, sortOrder, filterRoles, or customViewId, and 'Bigcapital list filters' is too generic to add meaningful semantic value beyond the schema.

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 the verb 'List' and the resource 'customers', so an agent can identify the core action. It does not explicitly differentiate from get_customer or list_vendors, but the resource name makes the purpose 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 about when to use this tool instead of related tools such as get_customer, create_customer, or list_vendors. The phrase 'using Bigcapital list filters' implies filtering is supported, but no conditions, exclusions, or alternative routing are provided.

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