get-a-wallet

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

With no annotations provided, the description carries the burden of disclosure. It clearly signals non-destructive, educational behavior through words like 'Lesson', 'Explains', and 'walks through', indicating it is informational rather than performing side-effectful actions.

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 three concise sentences with no fluff: it states curriculum position, target audience, and specific content. Each sentence adds value, and it is front-loaded with the key identifier 'Lesson 4'.

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 zero parameters and no output schema, the description fully covers what the tool does and what it covers. It gives enough detail for an agent to know exactly when and how to use it without needing additional context.

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 tool has zero parameters, so the description need not explain any. The baseline for 0 parameters is 4, and the description adds no confusion about parameter usage.

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 this is a lesson on installing a wallet, specifically targeting those without one. It distinguishes from siblings like 'what-is-a-wallet' by focusing on installation steps and tooling (npm, npx, skills CLI), not just conceptual explanation.

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 provides a clear use case: 'if you don't have one' a wallet, and identifies it as Lesson 4 in a curriculum, implying sequential usage. It doesn't explicitly name alternative tools but the use case is well implied.

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