Remember the agent wallet for buying

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

No annotations are provided, so the description must disclose behavior. It states the tool stores the wallet identity for the session and is a one-time prerequisite. However, it doesn't disclose details like whether repeated calls overwrite, what happens on invalid address, or what the return value is. It adds some context ('from @ton/mcp') but leaves out potential edge cases.

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 short sentences that are front-loaded with the primary action and context. No wasteful words, every clause adds value.

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 simple setup tool with no output schema, the description covers the purpose, session scoping, and call timing. It could mention expected return or error behavior, but with good schema coverage and clear context, it's sufficiently complete.

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 description coverage is 100%, with all four properties having descriptions in the schema. The description adds no additional parameter-level detail, relying on the schema. Baseline of 3 applies due to full 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 uses a specific verb 'Store' and identifies the resource (TON wallet identity) and its purpose (for buy tools). It clearly distinguishes from sibling buy tools by positioning itself as a prerequisite setup step. The title reinforces the same, but the description adds clarity about session scope and source.

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 call this tool ('Call this once before buying'), establishing it as a prerequisite. It explains the value proposition (so buy tools can target it), but doesn't explicitly mention alternatives or exclusions. This is clear enough for an agent to know this is a setup step before purchase tools.

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