billcom_list_bills

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

No annotations are provided, so the description bears full responsibility for behavioral transparency. It mentions routing and argument format but does not disclose side effects, pagination behavior, rate limits, or what happens when the operation fails. For a list operation, details about subset selection or ordering are missing.

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 relatively short but includes technical routing details (e.g., 'Routes through `/api/tools/invoke` under your JWT') that may not be actionable for the agent. It could be streamlined to focus on the operation's behavior and inputs.

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?

Although an output schema exists, the description does not mention what the tool returns (e.g., list of bills, pagination info). It also lacks context about authentication scope or the connector's capabilities. Given the absence of annotations, the description should provide more behavioral and return-value context to guide the agent.

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 single parameter `arguments` is a JSON string with zero schema description coverage. The description states it is 'JSON string of arguments for the connector operation', which adds minimal context beyond the schema's type constraint. It does not enumerate what keys or values are valid, leaving the agent to infer or guess the required structure.

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 tool name and description clearly indicate it lists bills from Bill.com. The phrase 'Billcom connector operation `list_bills`' and the `list_bills` in the name make the purpose evident. However, the description does not elaborate on the scope or filtering capabilities, which would help differentiate it from other billcom tools like `billcom_approve_bill` or `billcom_create_bill`.

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?

The description provides no guidance on when to use this tool versus other billcom tools or alternatives. It does not mention prerequisites, context, or typical use cases. The lack of usage heuristics leaves the agent without decision support for tool selection.

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