qbo_bills_create

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the creation action but doesn't mention side effects (e.g., vendor balance updates), permissions, rate limits, or any constraints beyond the schema. The description is insufficient for an agent to understand the tool's behavior.

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, succinct sentence that immediately conveys the purpose. It is front-loaded and wastes no words. However, given the tool's complexity (7 parameters, nested objects), a slightly more detailed description could be justified without losing conciseness.

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?

The tool definition relies heavily on the schema for parameter details. The description does not explain the return value (no output schema) or error scenarios. It provides minimal context beyond the creation action. While the schema fills many gaps, the description itself is incomplete for a full understanding.

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 100%, and each parameter has a detailed description (e.g., format for VendorRef, Line array structure). The description adds no extra parameter context beyond what the schema provides. Baseline score of 3 is appropriate as schema does the heavy lifting.

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 action ('Create'), resource ('Bill record'), and system ('QuickBooks Online'). It distinguishes this tool from siblings like qbo_bills_get or qbo_bills_update, and the tool name further differentiates it from similar create tools like qbo_purchases_create.

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 on when to use this tool versus alternatives (e.g., qbo_purchases_create, qbo_vendor_credits_create). There is no mention of prerequisites, conditions, or when not to use it. The description lacks any usage context.

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