quickbooks_create_bill

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

Annotations already carry idempotentHint=true, destructiveHint=true, and readOnlyHint=false, so the description need not re-state safety traits. It adds useful context: the routing preference ('governed connector authority'), the effect field being verified by Spring, and approval_ref being required when resuming a write. But it does not disclose what the mutation does to accounting records or reversibility, leaving the impactful write behavior under-explained.

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 structure is organized and front-loaded with the operation identity, followed by routing constraint and a clean parameter list. But the opening repeats 'QuickBooks connector operation create_bill (platform tool quickbooks.create_bill)' in two forms, and the parameter list largely restates names the schema already exposes since it is the sole documentation source. Reasonably compact, but not maximally efficient.

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 7-parameter tool with 0% schema description coverage and no enums, the description is incompletely specified. It never explains what fields belong in the `arguments` JSON, how bill creation behaves (draft vs posted, approval flow for write), or what prerequisites must hold. The presence of an output schema is a benefit, but the core invocation payload is the least documented element, leaving agents guessing when constructing the call.

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%, so the description must compensate, and it does give each of the 7 parameters a terse gloss (e.g., 'Stable business-action identity' for idempotency_key, 'Spring verifies it' for effect), which adds real meaning beyond the bare schema titles. However, the critical `arguments` parameter — the actual bill payload — is left as a vague 'JSON string of arguments for the connector operation' with no indication of required bill fields, a significant gap for the tool's core substance.

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 explicitly identifies the operation as the QuickBooks connector `create_bill` (platform tool `quickbooks.create_bill`), giving a clear verb+resource. The QuickBooks namespace distinguishes it from `xero_create_bill`, `clio_create_bill`, `billcom_create_bill`, `myob_create_bill`, and `quickbooks_pay_bill`. However, it never states what a bill is in QuickBooks (a vendor payable) or differentiates against `quickbooks_create_invoice`, so it falls 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 when-to-use information is present. The sentence 'Routes only through the exact project/account governed connector authority' is access constraint guidance, not usage guidance. There is no mention of prerequisites (e.g., vendor exists, connector account configured) or when one should prefer `quickbooks_list_bills`, `quickbooks_pay_bill`, or `quickbooks_create_invoice` instead. Nothing tells the agent how to choose this tool over alternatives.

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