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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the call is free, and it discloses the auditor's operational policies (safe-finality, fail-ambiguous matching, scan limits) and the per-batch credit cost model.

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?

A single front-loaded sentence with zero filler; the resource is named first and the payload contents follow as a compact list. Nothing is wasted and nothing essential is buried.

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 spelled out, and the description still previews the categories of information returned. Combined with the free-to-call note, an agent has enough to invoke it correctly, though a one-line steer toward sibling tools would make it 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?

The tool takes zero parameters, which is the baseline-4 case; there is no argument semantics to document. The description correctly spends no space on nonexistent inputs.

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 names a specific resource (the Base USDC Receivables Auditor) and enumerates the content of the returned overview: dual-RPC safe-finality policy, fail-ambiguous matching, scan limits, and per-batch credit cost. That is far more than a tautology, but it never distinguishes itself from siblings like get_payment_info or reconcile_usdc_receivables, so an agent must infer the boundary.

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?

Calling this 'Free' implies it can be called without spending credit, which is useful guidance and hints at a pre-flight/exploration use case. However, there is no explicit statement of when to use this versus reconcile_usdc_receivables or the other getters, and no exclusions, so usage is only implied.

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