qbo_deposits_list

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

No annotations are provided, so the description carries full burden. It states the tool lists records with pagination and date range, implying read-only, but does not disclose behavioral traits like rate limits, authentication needs, or whether it returns all deposits. The description adds minimal behavioral context beyond what parameters imply.

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, well-structured sentence that front-loads the core purpose. Every word contributes meaning without redundancy. It is highly concise.

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 list tool with 4 optional parameters and no output schema, the description is minimally adequate. It covers pagination and date filtering but lacks details on ordering, default behavior, or error responses. Oversights like not mentioning that startPosition is 1-based are covered by the schema, but overall completeness is average.

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%, so the baseline is 3. The description mentions 'pagination' and 'optional TxnDate range', which summarize parameters, but adds little meaning beyond the schema descriptions. It does not provide additional details like default values or interpretational guidance.

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 tool lists Deposit records with pagination and date range filtering. It uses a specific verb 'List' and identifies the resource 'Deposit records', distinguishing it from sibling tools like qbo_deposits_get or qbo_deposits_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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that for single deposit retrieval one should use qbo_deposits_get, nor does it specify 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.