Staking Stake Solayer

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds a note to confirm before writes but does not elaborate on side effects, state changes, or other behavioral traits beyond what annotations provide. Minimal added value.

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 four sentences long, front-loaded with purpose and context. It is relatively concise but includes some redundancy (e.g., 'SAP MCP context: Protocol staking; operation class write'). Still, every sentence serves a purpose.

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 existence of an output schema (not shown but indicated), the description covers purpose, usage, safety, and alternative tool groups. It is complete for a write tool, though it could briefly mention the output.

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%, so the input schema already describes both parameters (amount and wallet) sufficiently. The description does not add additional parameter-specific context or semantics beyond 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 the verb 'Stake', resource 'SOL', and destination 'sSOL via Solayer', distinguishing it from other staking tools like staking_stakeJupSOL and staking_stakeSOL. It also mentions it's a re-staking protocol with additional yield.

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 explicitly says 'Use for SOL and liquid staking flows' and provides pre-write checks. It also distinguishes from SAP staking tools and AgentKit staking tools, offering guidance on when to use this tool versus alternatives. However, it doesn't elaborate on when not to use it or specific sibling exclusions.

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