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

With no annotations provided, the description carries the full burden and discloses key behaviors: results are ready-to-sign tx objects with {to,value,data} for eth_sendTransaction, stake yields approve+stake while unstake/claim yield a single tx. It does not mention failure modes or auth, but covers the primary runtime 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?

Three sentences, front-loaded with the core purpose; each sentence adds a distinct detail (scope, action-specific output count, returned item shape) with no filler.

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 lack of an output schema, the description appropriately defines the return item structure, and the schema covers the parameter constraints. It explains the multi-transaction nature of stakes, so an agent has enough to invoke correctly, though it omits edge-case handling like insufficient allowance.

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?

Although the schema already documents all four parameters at 100% coverage, the description adds meaning by explaining the action-to-transaction-count mapping and the token specifics for each venue (MEGACHAD vs MC/MG LP), supplementing the schema's property descriptions.

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 the tool builds ready-to-sign staking transactions for stake/unstake/claim across two named venues, distinguishing it from AMM/swap/proposal builder siblings. Uses specific verb 'Returns ready-to-sign transactions' with explicit venue/action scope.

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?

Describes the two venue options and their corresponding tokens, plus the action-dependent output shape, giving clear context for when to invoke. Does not explicitly name alternative tools to avoid, but the scope is sufficiently bounded by naming the venues and actions.

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