pillar_direct_auto_compound

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

With no annotations, the description carries the burden and does add useful behavior: a keeper auto-boosts when sBTC accumulates above the trigger, no browser is needed, and gas is sponsored. However, it does not disclose what happens on reconfiguration or disabling, whether existing settings are overwritten, permission requirements, or what the call returns.

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?

Front-loaded with the core action and behavior, then supporting details. Slightly more than strictly necessary, especially the cross-sell tip, but no wasted sentences in the main explanation.

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 no annotations and no output schema, the description covers purpose, mechanism, signing model, and gas sponsorship. It remains incomplete for a configuration mutation because it does not say what happens to existing settings, how disabling interacts with an in-flight boost, or what the result looks like.

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%: `enabled`, `minSbtc`, and `trigger` are each documented in the schema, including units (sats). The description's mention of sBTC accumulating above the trigger loosely connects to `trigger` and `minSbtc`, but adds no semantics beyond the schema baseline.

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: 'Configure auto-compound for your Pillar wallet.' Clear what it does, but it does not distinguish itself from the very similar sibling tool `pillar_auto_compound` (nor from related direct tools like `pillar_direct_boost`).

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?

Explains how auto-compound behaves, but gives no guidance on when to use this tool versus alternatives such as `pillar_auto_compound` or `pillar_direct_boost`. The `earning_opportunities` tip is a cross-reference for yield, not a use-case selector.

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