create_deposit

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'create a bank deposit' without mentioning side effects, authorization needs, rate limits, or data persistence. An agent has no insight into what happens beyond creation.

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 very concise (one sentence, 8 words), which is efficient but sacrifices necessary detail for a complex tool with nested parameters and no output schema. It is not verbose, but it is under-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?

Given the tool's complexity (nested objects, no output schema, no annotations), the description is severely incomplete. It fails to explain what a deposit is in QBO, how line items relate to accounts, or what the response contains. This would hinder an agent's correct usage.

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 schema covers descriptions for most parameters (deposit_to_account_ref, line_items, txn_date, private_note), so the description adds no additional meaning. However, the schema coverage is 50% (context signal), meaning half of parameters may lack descriptions. The description does not compensate for this gap.

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 verb (Create), resource (bank deposit), and context (QuickBooks Online). It is specific enough to distinguish from sibling tools like create_invoice or create_payment, which deal with different financial documents.

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 provided on when to use this tool versus alternatives (e.g., create_transfer, create_journal_entry). There is no mention of prerequisites, required permissions, or scenarios where this tool is inappropriate.

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