Metis · Course Builder — Review Course

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

Without annotations, description lists checks performed but does not state side effects (read-only, no modifications), error conditions, or permissions needed. Adequate but not comprehensive.

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?

Well-organized with step number, purpose, bulleted checks, instruction, and parameter. No redundant sentences, all content earns its place.

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?

Mentions return of pass/fail report, but with output schema present, description need not detail return structure. Lacks prerequisites and report interpretation details.

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?

Single parameter 'slug' described as 'The course slug to review.' Schema coverage is 0%, so description adds basic meaning but not detailed syntax or examples.

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 'Run quality checks on a drafted course before publishing' and lists specific checks, distinguishing it from sibling tools like publish_course.

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 tells to fix failures before calling publish_course, implying usage timing. Does not mention alternatives or when not to use, but context is clear.

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