Fetch SAP Stake

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

Description aligns with annotations (read-only, idempotent). Adds context about being a read-only SDK wrapper on Solana RPC/SAP program, and its role in pre-mutation inspection. No contradictions.

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 sentences, front-loaded with main purpose, then context. Every word earns its place.

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 output schema exists, annotations cover safety, and description provides core behavior and usage context, the definition is complete and clear for an agent to use correctly.

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%, but description adds value by explaining the relationship between the two parameters (agentPda used when stakePda omitted). This semantic guidance exceeds schema 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?

Clearly states 'Fetch agent stake' with two options (by stake PDA or agent PDA). Distinguishes from other SAP fetch tools by targeting stake specifically.

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?

Provides context: use to inspect chain state before mutating accounts. Implicitly guides to use before mutation tools, but no explicit alternative for stake fetch.

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