publish_course

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

No annotations provided, so the description carries full burden. It clearly discloses that it marks the course as active, sets progress to 0, and writes a completion note. No contradiction with annotations since none exist.

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 short paragraphs: purpose/behavior, then usage timing, then Args/Returns. Every sentence contributes value. No redundant or wordy content.

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?

With one parameter and an output schema (though not shown), the description covers purpose, effect, usage timing, and return structure. Could mention prerequisites like requiring all 7 steps to be completed, but it already does. Minor gap: no details on what the completion note contains.

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 coverage is 0%, so description must compensate. The description adds 'The course slug to publish', which only rephrases the schema's 'Slug'. No additional format, examples, or constraints provided. Minimal added value.

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 the verb 'publish' and 'finalise', identifies the resource as a completed course build, and describes the specific database actions. Distinguishes well from sibling tools like 'review_course', 'save_course_outline', etc.

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 says 'Call after all 7 steps are done', indicating the prerequisite context. Does not mention alternatives or when not to use, but the purpose and sibling list provide sufficient guidance.

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