aruba_compare_invoice_totals

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

Annotations declare readOnlyHint=true and idempotentHint=true, indicating safe, repeatable execution. The description adds no behavioral context beyond the core action, such as what happens on mismatch (error vs. warning) or if totals are missing.

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, efficient sentence with no redundancy. It could be slightly improved by adding a brief second sentence on output, but remains appropriately 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?

Given the presence of an output schema, the description should hint at what the comparison returns (e.g., a boolean, a discrepancy report). It lacks this context, leaving the agent unsure what to expect after invocation.

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 should explain the 'xml_base64' parameter. It only generically implies the input is an XML document containing totals, failing to specify that it must be base64-encoded or the expected structure.

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 action 'Compare' and the specific resources 'document total with line and VAT totals.' It distinguishes this tool from siblings like 'aruba_extract_invoice_fields' or 'aruba_detect_invoice_anomalies' by focusing on a specific consistency check.

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 gives no guidance on when to use this tool versus alternatives (e.g., 'aruba_validate_invoice_xml_structure'). It does not mention prerequisites, such as needing to have extracted invoice fields first, or whether it should be used after parsing.

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