billy_list_bills

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

No annotations are provided, so the description must carry the full burden. It states READ-ONLY, implying no side effects, but lacks details on pagination, error behavior, or performance considerations.

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?

Extremely short, which is positive for conciseness, but the structure is a fragment. It front-loads the purpose but omits essential details, making it under-specified.

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 6 parameters, no output schema, and no annotations, the description is severely incomplete. The agent lacks crucial information to use the tool effectively, such as filter capabilities and response format.

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 0% and the description provides no information about the 6 parameters (page, state, pageSize, contactId, sinceDate, untilDate). The agent cannot infer their meaning or formatting without external knowledge.

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?

Clearly states it lists bills/expenses and marks it as read-only, distinguishing it from mutation tools like billy_approve_bill or billy_delete_bill. However, it does not differentiate from other list tools such as billy_list_invoices, which could cause confusion.

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 READ-ONLY tag gives a hint for safe usage, but there is no explicit guidance on when to use this versus other list tools, no prerequisites, and no alternatives mentioned.

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