Fetch SAP Session

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about being a 'Read-only SAP SDK wrapper against the configured Solana RPC and SAP program' and the purpose of inspecting chain state. This adds value beyond the annotations without contradicting them.

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 two sentences long, with the first sentence stating the core purpose and the second providing usage context. Every word is earned; there is no redundancy or unnecessary detail. Front-loaded with the most critical information.

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?

The tool has an output schema (indicated by context), so the description does not need to explain return values. The description covers purpose, usage guidelines, and parameter sufficiently for a simple read-only fetch tool. No gaps are apparent.

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 input schema has 100% description coverage, with the sessionPda parameter already fully described as 'Session PDA (base58) to fetch the ledger for'. The description does not add additional meaning or format details beyond what the schema provides. Baseline 3 is appropriate.

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 fetches a session ledger by session PDA (specific verb and resource). It adds context about being a read-only SDK wrapper, but does not explicitly differentiate from sibling tools like sap_fetch_escrow or sap_fetch_stake. The mention of 'session ledger' and 'session PDA' is specific enough to imply uniqueness.

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 states when to use this tool: 'Use these reads to inspect current chain state before mutating...' This provides clear guidance on the appropriate context (pre-mutation inspection) and implicitly tells the agent not to use it for mutation. No alternatives are listed, but the usage context is strong.

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