automated_reconciliation__one_to_many_match

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only describes the basic operation without mentioning side effects (e.g., mutation, read-only), error handling, performance characteristics, or what happens when no combination is found. This leaves the agent inadequately informed about the tool's behavior.

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 concise sentence that immediately conveys the core function with no extraneous words. It is well-structured and efficiently uses space.

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 (one-to-many matching, four parameters, nested objects), the description is too brief. It lacks information about return values, parameter constraints (e.g., positive amounts, integer limits), and edge cases (no match, multiple matches). With no output schema or annotations, the description should provide more context to be complete.

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?

With 0% schema description coverage, the description must compensate. It explains that 'target' is the amount to match and 'candidates' are items to combine, providing basic meaning. However, it does not clarify 'tol' (likely tolerance) or 'max_combo' (maximum number of candidates), which are critical for correct usage. The description adds some value but falls short of fully compensating for the schema deficit.

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's purpose: 'Find a combination of candidates summing to the target amount (batched settlements).' The verb 'Find' and specific resource 'combination of candidates summing to target amount' make it distinct from siblings like 'exact_match' and 'tolerance_match', which focus on single matches or tolerance-based matches.

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 phrase 'batched settlements' implies a use case for reconciling batches where multiple items sum to a target, but the description does not explicitly state when to use this tool versus alternatives like 'exact_match' or 'tolerance_match'. No exclusion criteria or when-not-to-use guidance is provided.

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