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

With no annotations, the description carries the full burden for behavioral disclosure. It transparently states that only placeholders are created ('no content yet') and that it returns lesson ids for a follow-up loop, revealing the composite create behavior. It does not mention potential side effects, permissions, or idempotency, but for a create-style tool, the essential behavior is clearly conveyed.

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?

The description is three sentences, all of which are information-dense and earn their place. It front-loads the primary action, then explains the follow-up, then gives a clear usage preference. There is no repetition or fluff.

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?

The tool is fairly complex (11 params, nested objects, no output schema), and the description provides a solid high-level overview but leaves gaps. It explains the course outline concept and the follow-up update step, but it does not describe the full return structure (e.g., course id, module ids) or any prerequisites. Since there is no output schema, the description should more fully cover return values and overall 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 only 9% (only 'modules' has a description). The description adds some meaning by explaining lessons as 'title/description only' and implying that 'title' is the course title, but it does not cover the many other parameters (tags, difficulty, visibility, etc.) nor provide any syntax or format details. With such low coverage, the description should compensate more than it does.

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 uses a specific verb 'Scaffold' and names the exact resource scope: 'course + modules + lesson placeholders (title/description only, no content yet).' This clearly distinguishes it from sibling tools like hivelearn_create_course (which likely creates only a course) and hivelearn_create_lesson/module, by emphasizing the one-call combined creation.

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?

The description provides explicit context: 'This is the preferred first step when authoring a new course from a plan.' It also gives a direct follow-up instruction: 'loop over the returned lesson ids with hivelearn_update_lesson_content.' However, it does not state when NOT to use this tool or name alternative approaches (e.g., using hivelearn_create_course + create_module + create_lesson), so it lacks full exclusion guidance.

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