pillar_boost

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that the tool opens the Pillar website Boost tab for amount selection and confirmation, explains the Zest supply/borrow/re-supply mechanics, and details the automatic DCA behavior above 100,000 sats. It omits prerequisites such as wallet connection and risks of leveraged positions, but provides substantial disclosure beyond the schema.

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 main purpose, then mechanics, alternative, DCA behavior, and a tip. It is slightly long but every sentence contributes useful context; no major redundancy.

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 the complexity of a leveraged position tool with no annotations or output schema, the description covers what it does, how it works, the non-leverage alternative, and the DCA threshold behavior. It could mention setup prerequisites or wallet connection requirements, but is otherwise complete enough for an agent to act.

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% for the single optional amount parameter, so baseline is 3. The description adds meaningful semantics: amounts over 100,000 sats trigger DCA, split into daily 100k-sat chunks with a 700k-sat maximum per schedule, and the first chunk executes immediately.

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: 'Create or increase a leveraged sBTC position (up to 1.5x) on your Pillar smart wallet.' It also names the non-leveraged alternative (pillar_supply), making the tool's distinct purpose clear.

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?

Explicitly directs agents to pillar_supply for simple yield without leverage, which is the key decision point. It does not address the nearby pillar_direct_boost sibling, but the main alternative and DCA threshold conditions are clearly stated.

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