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

The description goes far beyond annotations by detailing in-memory signing, submission to Solana, and the return of a confirmed signature. It also discloses secret key handling (never stored, logged, or forwarded) and suggests verification via verify_code_integrity, adding significant trust context beyond the basic readOnly/destructive flags.

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 three sentences long, front-loaded with the core purpose, and every sentence earns its place: workflow, return value, and security/verification. No redundancy or fluff.

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 single-call staking tool, the description covers the essential behavioral elements: what it does, how it handles the key, what it returns, and who should use it. Without an output schema, mentioning the confirmed transaction signature is sufficient. The description also differentiates from many sibling tools by noting it is one-shot and recommended for autonomous agents.

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?

With 100% schema description coverage, the baseline is 3. The description adds crucial semantic meaning for the secretKey parameter, explaining it is used only for in-memory signing and never stored, which enriches the schema's generic description. It does not add much for walletAddress or amountSol beyond what schema already provides.

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 'Stake SOL with Blueprint validator in a single call' and describes the full workflow (build, sign, submit). It distinguishes from sibling tools like create_stake_transaction and submit_transaction by emphasizing the one-shot nature and the confirmed transaction signature return.

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 identifies this as 'the recommended tool for autonomous agents,' providing clear context for when to use it. However, it doesn't explicitly name alternatives or state when not to use this tool versus simulated or multi-step alternatives.

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