create_module

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only says 'Create a new module,' which implies mutation but does not mention permissions, side effects, idempotency, or error conditions. The hint to list modules first is the only extra context, but it is not a disclosure of tool behavior.

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 two sentences, front-loaded with the primary action. The second sentence provides a helpful tip without wasting words. No redundancy or filler.

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 description is minimally adequate for a create operation with a rich schema. It lacks details about return values, permission requirements, or what happens when optional fields like position or unlock_at are omitted. The absence of annotations and output schema raises the need for more context, but the tool is simple enough that this may be the minimum viable.

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 100%, so all parameters are already documented in the schema. The description adds no parameter-specific meaning beyond the schema, which is acceptable per the baseline of 3. It does not confuse or restate what the schema already provides.

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 states a specific verb and resource: 'Create a new module in a course.' This clearly distinguishes it from sibling tools like update_module, delete_module, and list_modules. The purpose is unambiguous.

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 gives actionable guidance: 'Use list_modules to see existing modules first.' This suggests a proper workflow and helps avoid duplicates, though it does not explicitly contrast with update_module or other alternatives. Still, it provides useful context for when to use this tool.

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