what-is-usdc

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

The description accurately conveys the tool is an educational resource with no side effects or destructive actions. No annotations exist, so the description adequately communicates safe, read-only behavior.

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 efficiently conveys the tool's purpose, content, and curricular position. No unnecessary words or repetition.

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 lesson with no parameters or output schema, the description fully captures what the user will learn. It is complete and self-contained.

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 exist, and the description adds context about the lesson's content beyond the empty schema. Baseline score of 4 is appropriate for zero-parameter tools with informative descriptions.

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 lesson about USDC, its role as default currency for agent payments, and blockchain considerations. It distinguishes from sibling lessons that cover different topics.

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 when learning about USDC but provides no explicit conditions for when to use versus other lessons or alternatives. No guidance on prerequisites or exclusions.

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