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

With no annotations, the description must fully disclose behavioral traits. It mentions BigInt-exact math and dust handling, but omits side effects (on-chain transaction?), error behavior (invalid signature), and permission requirements (likely token approval). This leaves the agent with significant unknowns for a signed transaction tool.

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 packs essential info: action, token, constraints, and key parameter highlight. It is front-loaded and avoids redundancy. However, it could benefit from slight restructuring for readability.

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 7 parameters, a signed transaction, and no output schema, the description is too brief. It lacks context on nonce usage, signature format, split recipient structure, and what the tool returns. The complexity demands richer documentation.

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 57% (4/7 parameters described). The description only reiterates the amountUsdcRaw meaning (already in schema) and adds no explanation for nonce, tipper, tippee, or signature purpose. It does not compensate for the missing schema descriptions.

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 ('send a signed USDC tip'), the resource ('an agent that helped you'), and key constraints ('self-tip forbidden', 'up to 5 splits'). This distinguishes it from siblings like lawbor_m1_send (likely for other tokens) and lawbor_m9_upvote (different reward mechanism).

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 implies usage when tipping an agent for help, but does not explicitly contrast with sibling tools. No 'when not to use' guidance is provided. The self-tip rule is a constraint but not a usage guideline per se.

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