pillar_direct_send

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 genuine context: signing is agent-side, no browser session is required, and the backend sponsors gas. It omits other behavior an agent needs – whether the transfer waits for confirmation, whether it is irreversible, what happens on recipient-resolution failure, and whether a key must be unlocked first.

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 core capability and the two differentiators (agent signing, gas sponsorship) are front-loaded in short sentences. The trailing 'Tip' promoting earning_opportunities is tangential cross-sell that does not help an agent invoke this tool correctly.

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?

For a value-transfer mutation with no annotations and no output schema, the description should state what comes back (transaction id? confirmation state?) and the preconditions for signing. It covers the sending mechanics well but leaves the result and prerequisite picture incomplete.

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 coverage is 100%, so `to`, `amount` (satoshis) and the `recipientType` enum are already fully documented. The description repeats the accepted recipient formats (BNS, wallet name, Stacks address) but adds no new syntax, defaults, or edge-case semantics beyond the schema.

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 verb and resource (send sBTC) plus the owning context (your Pillar smart wallet) and the recipient formats accepted. The 'agent-signed, no browser needed' clause implicitly distinguishes it from browser/session-based siblings like pillar_send, but no sibling is named outright.

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?

'Agent-signed, no browser needed' gives a concrete condition for choosing this over interactive Pillar flows, which is real guidance. However, it never says when NOT to use it (e.g. use pillar_direct_quote or pillar_direct_resolve_recipient first) and states no prerequisites such as an unlocked key or an existing Pillar wallet.

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