list_items

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

With no annotations provided, the description carries the full burden of explaining behavior. It only says 'List ... using Bigcapital list filters' and says nothing about pagination, default sorting, whether an empty filter returns all items, permissions, or response shape. The read-only nature is weakly implied but not disclosed.

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 concise sentence with no filler or repetition. However, it is so terse that it misses the opportunity to include key constraints, so it is efficient but not fully informative.

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?

For a tool with six parameters, no output schema, and no annotations, this description is insufficiently complete. An agent cannot determine how filters combine, what a list response contains, or whether parameters like customViewId are required for certain views.

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%; only sortBy and searchTerm have descriptions. The description adds no parameter-level meaning, and terms like filterRoles, customViewId, and viewSlug remain undocumented. The phrase 'Bigcapital list filters' provides only vague context and does not compensate for the low coverage.

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 a clear action ('List') and resource ('items'), which distinguishes it from sibling list_* tools like list_customers and list_vendors. It does not explicitly describe the scope of the list or clarify what 'items' means in Bigcapital, so it falls just short of a 5.

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 versus alternatives such as get_item or update_item, nor any conditions under which one should use different filter parameters. The only usage hint is the generic phrase 'Bigcapital list filters'.

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