education_getChecklist

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

Without annotations, the description reveals it returns questions with short warnings. It does not mention side effects or destructive actions, which is appropriate for a read-only tool. Could add more detail about response structure, but 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?

Efficiently front-loaded with purpose, then usage, then categories list. Every line adds value; 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?

Despite no output schema, the description explicitly states what is returned (questions with warnings). It also names the sibling tool for follow-ups, covering all necessary context.

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 single category parameter has an enum with full schema description. The description adds critical warnings for each category (e.g., USDC has 6 decimals), providing significant value beyond the schema.

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 it gets an interactive checklist for a specific category, lists categories with critical warnings, and distinguishes from sibling tool education_explainLesson by noting its use for deep dives.

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?

Provides explicit guidance to walk developers through teaching moments, details each category with critical notes, and explicitly recommends education_explainLesson for deeper explanations.

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