pillar_fund

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

With no annotations, the description carries the full burden. It usefully discloses that 'exchange' generates a deposit address, 'btc' auto-converts to sBTC, and the tool opens the frontend with the appropriate deposit flow. It does not state authentication requirements, whether funds move immediately, fee implications, or other operational constraints.

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 front-loaded with the core purpose and structured as a short, scannable method list. Every sentence adds useful context or a relevant follow-up tip without unnecessary repetition.

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 two-parameter tool with full schema coverage and no output schema, the description is largely complete. It explains the funding methods and the frontend-opening behavior. It could be stronger by noting wallet connection or authentication requirements, but the key invocation context is present.

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 the baseline is 3. The description adds value beyond the schema by explaining the method-specific outcomes, such as generating a deposit address for exchanges and auto-converting BTC to sBTC. It does not mention the optional amount parameter, but that is already well documented in 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?

The description clearly states a specific verb and resource: fund a Pillar smart wallet. It enumerates the three supported funding methods, so the agent knows the scope. It does not explicitly differentiate this tool from sibling funding or supply tools such as pillar_supply or pillar_direct_supply.

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 explains which method corresponds to which funding source, which gives implied guidance for choosing a method. However, it provides no explicit when-to-use or when-not-to-use guidance relative to sibling tools, and no prerequisites are stated.

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