fund-my-wallet

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

No annotations provided. Description conveys it is an informational lesson with no side effects, but does not elaborate on expected behavior or outputs.

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?

Single sentence front-loading the key identity ('Lesson 6 of the curriculum') and concisely listing 3 covered methods. Every word earns its place.

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?

Adequately describes content covered but omits context like learning objectives, prerequisites, or follow-up actions. Acceptable for a simple lesson but could be more 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?

No parameters defined (100% schema coverage). Description does not need to add parameter details; baseline 4 applies.

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?

Clearly identifies itself as 'Lesson 6 of the curriculum' and explains its purpose: 'How USDC gets into your wallet.' Distinguishes from sibling lessons like 'what-is-usdc' by being about the funding process.

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?

No explicit guidance on when to use this tool versus alternatives. Does not mention prerequisites or sequence in the curriculum.

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