what-is-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 transparently explains that the tool is an educational lesson, describes its topic, and notes it assumes no prior knowledge. While it doesn't detail the output format, for a static lesson tool this is sufficient context about what to expect.

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, front-loaded with the lesson number and topic, and contains no superfluous words. Every sentence adds value by specifying position in curriculum and prerequisites.

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 the low complexity of this educational tool and the empty schema/annotations, the description is adequately complete. It covers what the lesson is, its position, and intended audience. A slightly longer description could mention how it relates to sibling lessons, but the current level is sufficient.

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 baseline is 4 per the rubric. The description appropriately focuses on the lesson content rather than parameter details, which are nonexistent. No additional parameter semantics are needed.

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 is 'Lesson 1 of the curriculum' and explains its content: 'What a wallet is and what it lets you do.' This distinguishes it from sibling tools like 'what-is-x402' and 'what-is-usdc' which cover other topics, and positions it as the foundational lesson.

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 signals usage by stating it is 'Lesson 1' and 'Assumes no prior knowledge of cryptography or blockchains.' This implies it is the starting point for beginners, but it does not explicitly mention alternative tools or when not to use it, leaving some ambiguity.

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