motimate_create_moti

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

With no annotations provided, the description carries the disclosure burden. It adds one meaningful behavioral fact: chapters must be added later via the Motimate interface. However, it does not mention return values, permissions, or duplicate-creation behavior, leaving some behavioral ambiguity.

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 tight, front-loaded sentences: the first states the action and scope, the second lists the affected fields, and the third gives a key limitation. Every sentence earns its place with no redundancy.

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 plus the fully documented schema provide enough to call the tool correctly for the initial creation step, and the chapter caveat prevents a false expectation. However, with no output schema and no annotations, the description leaves return/confirmation behavior and side-effect details unstated.

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 the schema already documents every parameter. The description's list of settable fields maps to most parameters but adds no new semantic detail beyond the schema; locked_order is not mentioned in prose, though the schema covers it.

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 opens with a specific verb and resource: 'Erstellt eine neue Schulung (Moti) in Motimate.' The word 'neue' clearly separates creation from the sibling motimate_update_moti, and listing the settable fields makes the tool's scope 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?

It is clear from 'Erstellt eine neue Schulung' that this tool is for creating a new Moti, and the closing sentence sets the boundary that chapters cannot be added through this tool. It does not explicitly name alternatives like motimate_update_moti, but the context is strong enough.

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