Metis · Course Builder — Save Course Curriculum

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

No annotations provided, so description carries the burden. It discloses file write destination (`knowledge/courses/{slug}/course.json`) and state advancement (to Step 5). However, it omits side effects, error handling, permissions, or validation behavior. For a mutation tool with no annotations, this is adequate but not fully transparent.

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?

Two sentences plus argument list. Front-loaded with purpose and step. No redundant information. Every sentence serves a purpose.

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?

Output schema exists (though not shown) so return value documentation is not needed. Description explains the step context and file writing. Lacks details on error cases or input validation, but is sufficient for a simple 2-param tool within a larger workflow.

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?

Schema description coverage is 0%, so description adds essential meaning: slug as course identifier, curriculum_json as JSON with modules and lessons arrays. This compensates for empty schema descriptions. Could be strengthened by detailing the structure of modules and lessons.

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?

Description clearly states verb 'Save' and resource 'approved curriculum design for a course'. Identifies as Step 4 in a workflow, distinguishing it from sibling tools like save_course_outline (earlier step) and save_course_sources (different content).

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?

Explicit guidance: 'Call this after the Learning Architect has produced the curriculum.' Provides context on when to use, but lacks when-not-to-use or alternatives. Workflow context (Step 4) helps agents understand ordering.

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