creer_cours

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

No annotations, so the description carries the full burden. It hints that a local working folder is created (a filesystem side effect) but says nothing about idempotency, what happens on duplicate titles, required permissions, or error behavior for what is clearly a mutating operation.

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?

A single front-loaded sentence with no filler; the action and input come first. Slightly terse for a creation tool but structurally clean.

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?

An output schema exists, so return values need not be explained. However, for a creation tool with no annotations and no usage or behavioral detail, the description leaves the agent short of what it needs to call it confidently in edge cases.

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% and only one parameter exists. The phrase 'à partir d'un titre' confirms the parameter is a title, but that merely restates the field name 'titre' with no format, length, or uniqueness constraints. It only marginally compensates for the missing schema documentation.

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?

States a specific verb (Crée) and resource (un cours local / dossier de travail) and clarifies it is derived from a title. It does not differentiate itself from siblings like detail_cours or liste_cours, so an agent gets the action but not the routing logic.

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?

No when-to-use context, no prerequisites, and no mention of alternatives. The agent is not told when creating a new course is appropriate versus listing or viewing existing ones.

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