get_solana_setup_status

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

Annotations already indicate read-only, non-destructive, idempotent. Description adds: cheap chain-read, one getAccountInfo per PDA, no SDK load, no oracle fetch, never throws, returns empty arrays for empty wallet. No contradiction.

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?

Description is concise (~100 words), front-loaded with 'READ-ONLY' and purpose. Structured with usage guidance, technical details, and edge cases. No unnecessary sentences.

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 no output schema, description fully explains return values (durable-nonce fields, MarginfiAccount PDAs) and edge case (empty wallet). Covers all context needed for a single-parameter read-only probe.

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?

Parameter wallet has a detailed schema description covering format and return info. Tool description adds little beyond stating it probes setup pieces; schema already provides value. Baseline 3 due to high schema coverage.

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 it probes Solana wallet setup pieces (durable-nonce and MarginfiAccount PDAs). It uses specific verbs and resource references, and distinguishes itself from siblings by mirroring get_ledger_status pattern.

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?

Explicitly advises calling before multi-step Solana flows to skip redundant prepare_* calls. Provides concrete scenario and alternative (avoid re-proposing). Clear when and why to use.

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