fund-my-wallet

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

With no annotations, the description carries the burden of explaining behavior. It states the lesson number and outlines exactly what topics will be covered, which tells the user what to expect. It doesn't discuss side effects or prerequisites, but as a lesson tool, this is sufficient.

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, front-loaded with 'Lesson 6 of the curriculum,' and uses concise language to list coverage areas. Every word earns its place without redundancy.

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 informational lesson with no output schema and no annotations, the description gives enough context about the lesson's content and position in the curriculum. It could mention prerequisites or how the lesson is delivered, but this is not necessary for basic comprehension.

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 schema has zero parameters, and the baseline for 0 params is 4. The description adds no parameter-specific details, but none are needed since there are no parameters to describe.

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 identifies the tool as a curriculum lesson about getting USDC into a wallet, listing three specific coverage areas. It is distinct from sibling tools (e.g., what-is-a-wallet, get-a-wallet) by focusing on the funding process, though it doesn't explicitly name alternatives.

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 context implies usage when a user needs to learn how to fund their wallet, but there is no explicit 'use this when' or guidance on when to choose it over sibling lessons. Alternatives are not mentioned, leaving the decision to the user.

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