connect_drop

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the operation is a write/execution, that results may still be processing (202), and that retries should reuse the idempotencyKey. It does not mention side effects, failure modes, or auth requirements, but the idempotency and async-status traits are valuable.

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 dense sentence that front-loads the core purpose and then adds the most important operational details. There is no filler or repetition of the schema.

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?

The tool has six parameters, nested recipient objects, no annotations, and no output schema. The description explains status codes and idempotent retry but does not clarify required payment fields, chain behavior, token/amount semantics, or failure handling, so an agent lacks enough context to invoke it reliably.

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 0%, so the description must compensate for six parameters. It adds semantic insight only for idempotencyKey via the retry note and broadly hints at recipients via 'batch token transfer.' chainId, tokenContract, amountInWeiPerRecipient, and ignoreFailedRecipients remain unexplained, leaving key decision-making to the agent.

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 verb and resource: 'Execute a Smart Send (batch token transfer).' It is distinct from the lookup/pricing siblings, though it does not explicitly name or contrast any alternative such as connect_drop_balance.

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 establishes the execution context and the idempotency-based retry behavior, but it does not explicitly state when to choose this tool over siblings. The 201/202 statuses and 'retry with same idempotencyKey' provide clear operational guidance.

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