publish_course

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

No annotations exist; description reports it marks row as active, sets progress, writes note. It does not disclose reversibility, permission needs, or potential side effects beyond the stated changes.

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?

Very concise, front-loaded purpose, structured with Args/Returns, every sentence adds value. No waste.

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 main action, preconditions (after 7 steps), and return value. Lacks details on error handling, prerequisites (e.g., must a course exist?), or what happens if called prematurely.

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?

Only one parameter (slug) with 0% schema description coverage. Description adds minimal meaning ('The course slug to publish') but does not elaborate on format or validation.

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?

Clearly states it finalizes and publishes a course, marks as active, sets progress, writes note. Distinguishable from siblings like start_course_build or save_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 says 'Call after all 7 steps are done', providing clear context. Lacks explicit alternatives or when-not-to-use, but the single instruction is strong.

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