get_solana_setup_status

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

The description adds significant value beyond annotations. It specifies the tool is 'READ-ONLY', cheap (one getAccountInfo per PDA), has no SDK load or oracle fetch, and never throws for an empty wallet. This aligns with annotations (readOnlyHint, idempotentHint) and provides additional useful behavioral context.

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 somewhat lengthy but well-structured, front-loading key information ('READ-ONLY — probe...'). Every sentence adds value, though it could be slightly more concise without losing clarity.

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 description fully explains the return values (exists, address, nonce value, authority for nonce; index and address for PDAs) and error behavior (never throws for empty wallet). Since there is no output schema, the description carries the full burden and meets it completely.

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 covers the single parameter with description, achieving 100% schema coverage. The description adds extra context about what the parameter returns (durable-nonce state and MarginfiAccount PDAs), going beyond the schema's description.

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 explicitly states it is a READ-ONLY probe to check which one-time setup pieces (durable-nonce account and MarginfiAccount PDAs) are in place for a Solana wallet. It uses specific verbs and resource names, and distinguishes itself from siblings by referencing the '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?

The description clearly states when to call the tool: 'BEFORE planning a multi-step Solana flow (nonce init → MarginFi init → supply)' to avoid redundant prepare_* calls. It also explains that empty arrays are returned when nothing is set up, guiding agents to skip unnecessary steps.

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