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

With no annotations, the description carries the full burden and does add real context: the destination wallet, the network (Base), and the 1 USDC = $1.00 conversion. However, it omits idempotency behavior (calling twice with the same hash), what happens on an unconfirmed or invalid transfer, and whether the credit is reversible — all material for a credit-granting mutation.

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?

Three tight sentences, front-loaded with the purpose and then the operational steps. Every sentence earns its place, though the wallet address and conversion could be consolidated.

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 exists, and there are no annotations, so the description should ideally say what a successful call returns (credited amount, confirmation) and how verification failure surfaces. It covers the happy-path flow well but leaves the mutation's edge behavior undocumented.

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?

Schema description coverage is 100%, so tx_hash and agent_id are already documented, including agent_id's origin from create_concierge. The description's 'call this with the transaction hash' adds no meaning beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific compound action (verify a USDC transfer + credit the equivalent USD) on a named resource (Personal Shopper). The [PERSONAL SHOPPER] tag scopes it, and the operation is clearly distinguishable from siblings like confirm_purchase or redeem_points.

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?

Gives a clear prerequisite workflow: send USDC on Base to the stated wallet, then call this with the tx hash. This tells the agent exactly when this tool applies. It stops short of stating exclusions or what to do if the transfer hasn't confirmed, but the ordering constraint is explicit.

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