find_unallocated_transactions

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the semantic meaning of 'unallocated' but nothing about result size, pagination, or how date bounds affect output. With annotations carrying the behavioral load, this is weak but not contradictory.

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?

It is short and front-loaded, but it is a noun fragment rather than a complete statement, so its brevity reflects under-specification rather than efficient conciseness. It conveys one fact and omits everything else an agent needs.

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?

An output schema exists, so return values need not be explained. However, for a parameterized find tool with one required and two optional parameters, the description supplies no invocation context, no date-range semantics, and no routing to alternatives.

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% and the description never mentions from_date, to_date, or resource. The required 'resource' parameter is particularly ambiguous and is undocumented in both places, so the description does nothing to compensate.

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 fragment identifies a specific resource and condition: receipts/payments lacking AR/AP invoice allocation on any line. That scope clearly separates it from siblings like find_duplicate_transactions or find_broken_invoice_references. It stops short of a verb ('List/Find'), so it reads as a definition rather than an action.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternative sibling tools such as find_records or ledger_transactions. The reconciliation use case must be inferred entirely from the tool name.

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