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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is known. The description still adds value: it reinforces read-only, explains that writes happen through other tools, and imposes a confirmation gate on uncertain lines – context beyond what annotations convey.

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?

Front-loaded with the action and scope, and the included detail (entry types, sure flag, confirmation rule) earns its place for a tool with no output schema. The middle sentence is dense and slightly run-on, costing a point against ideal 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?

With no output schema, the description carries the burden of describing returns, and it does so well: it enumerates the entry types (expense/transfer/payment/deposit), the sure flag, and pending transactions as separate. An agent has enough to call it and interpret results, though pagination/volume behavior is unspecified.

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 schema fully documents 'company' and 'sure_only'. The description gestures at the 'sure' concept but does not explain the parameters (e.g., what 'company' accepts or how sure_only filters), so it adds nothing meaningful beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('List the bank transactions QuickBooks has not booked yet') and qualifies the scope (connected bank accounts, pending listed apart). The unbooked-feed framing distinguishes it from siblings like list_bank_transactions and find_bank_transactions_not_in_books without needing either schema.

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?

Explicitly routes the booking action to 'the regular create tools when the user asks' and states that non-sure lines 'need the user's confirmation first' – a clear workflow condition. It stops short of naming which sibling to call for adjacent needs, so it's slightly below a full when/when-not/alternative statement.

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