pillar_direct_stacking_status

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

With no annotations, the description carries the full burden and does well: it declares the operation read-only and signing-free, then enumerates the data returned (locked vs liquid STX, current PoX cycle, dual stacking enrollment). Missing only details like permission/wallet-state prerequisites or freshness/caching behavior.

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?

Two tight sentences plus a short tip; the core purpose and read-only nature are front-loaded and there is no filler. The earning_opportunities tip is only loosely related to checking status, slightly diluting focus.

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 zero-param, no-annotation, no-output-schema tool, the description compensates by spelling out exactly what information comes back. It is nearly sufficient to call correctly; only guidance on which overlapping stacking-status sibling to prefer is absent.

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?

The tool takes zero parameters, so there is nothing to document and the baseline of 4 applies. The description correctly implies no inputs are required by framing it as a simple status read.

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 (check) and resource (stacking status) scoped to the Pillar smart wallet, and summarizes what is shown (STX locked vs liquid, PoX cycle, dual stacking enrollment). It does not explicitly distinguish itself from sibling status tools like get_stacking_status, dual_stacking_status, or pillar_dca_status, so the Pillar scoping is the only differentiator.

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 'no signing needed — reads on-chain data' line implies when this is appropriate (a read-only status check), and the tip routes to earning_opportunities for follow-up. However, it never states when to use this versus get_stacking_status or dual_stacking_status, which overlap heavily, so guidance is implied rather than explicit.

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