Attempt Auto Reconciliation

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

Annotations indicate it's not read-only, not destructive, not idempotent, but the description does not elaborate on side effects, success/failure behavior, or retry safety. Minimal behavioral disclosure beyond the annotation flags.

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?

One sentence and an args list; not verbose but could be more compact. The structure is functional but lacks front-loading of key information.

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?

No output schema and no description of return value. The complex nested parameter 'body' lacks detailed subfield documentation. Context about what the tool returns or when it's appropriate is missing.

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?

Single parameter 'body' with vague description in schema. The description adds 'carrierInvoiceId, etc.' hinting at required fields, but the schema allows any additional properties. Schema coverage is 100% but lacks structural detail.

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?

Description states 'Attempts automatic reconciliation of carrier invoices' which is a clear verb+resource. However, it does not distinguish from sibling tools like get_carrier_invoices or get_carrier_invoice_entries.

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?

No guidance on when to use this tool vs alternatives, nor any prerequisites or conditions. The description lacks context about when auto reconciliation is applicable.

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