move_lesson

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

No annotations provided; description lists parameters but lacks key behavioral details like side effects on other lessons or timestamps.

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?

Short paragraph plus bullet list; every sentence is necessary and well-organized.

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?

Covers use cases and parameters; output schema exists to describe return value, reducing burden on description.

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?

Adds meaningful descriptions for each parameter (e.g., 'same as source to reorder' for target_chapter, 'New 0-based position' for idx) beyond schema names.

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?

Uses verb 'move' and resource 'lesson' clearly; distinguishes from sibling 'reorder_chapter' by specifying action on lessons.

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?

Explicitly states moving to different chapter or reordering within same chapter; does not specify when not to use but implies context.

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