Receipt Batch

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that create modes require explicit approval, which is useful but lacks details on what 'explicit approval' entails or what the tool does beyond modes.

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 sentence that front-loads the key modes. It is concise and avoids redundancy, though it may be too terse for complete clarity.

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 11 parameters and no output schema, the description should provide more context about what the tool achieves (e.g., creating accounting entries) and expected outputs. The current description only covers modes, leaving significant gaps.

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 100% schema description coverage, each parameter is well-documented in the schema. The tool description adds no extra parameter meaning, meeting the baseline of 3.

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 handles receipt batches with four modes (scan, dry_run, create, create_and_confirm). It differentiates the tool from siblings by focusing on batch processing, though the overall goal ('merged receipt batch') could be more explicit.

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 explains the modes but provides no guidance on when to use this tool compared to siblings like 'create_purchase_invoice_from_pdf' or 'accounting_inbox'. There is no when-not-to-use or alternative tool mention.

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