what-is-usdc

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

No annotations are provided, so the description carries the burden. It clearly indicates this is an educational lesson, implying no side effects. However, it does not explicitly state it is read-only or that it returns informational content, but the nature of the tool is evident from the name and description.

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 a single sentence that front-loads the curriculum position ('Lesson 2') and concisely lists the three content areas. No wasted words.

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 parameters and no output schema, the description adequately covers the content. It does not mention prerequisites or next steps, but the curriculum context and sibling tool names partially fill that gap.

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 schema is trivially complete. The description correctly does not attempt to add parameter semantics. Baseline for zero parameters is 4.

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 'Lesson 2 of the curriculum' and specifies the topic: what USDC is, why it's the default currency for agent payments, and the importance of blockchain choice. This distinguishes it from siblings like 'what-is-x402' and 'what-is-a-wallet'.

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 implies use as part of a curriculum sequence ('Lesson 2'), but does not explicitly state when to use this tool over alternatives or provide exclusions. There is no guidance on prerequisites or progression, though the curriculum context gives some hint.

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