create_lessons

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

Annotations provide only generic hints (readOnly=false, idempotent=false, destructive=false). The description goes far beyond them by disclosing batch processing semantics, per-row independence, the need to check 'failed', the OAuth scope requirement, type-specific validation rules, and the append behavior for omitted 'order'.

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 dense but every sentence and bullet carries actionable information. It front-loads the batch requirement, then organizes constraints by type, then covers optional behavior and error handling. There is no fluff or repetition of schema content.

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?

Given the sparse schema and high payload complexity, the description is exceptionally complete: it defines the required shape of each lesson, the three supported types and their mutually exclusive content fields, limits, optional fields, ordering behavior, partial-failure handling, and required OAuth scope. An output schema exists, so return-value documentation is not needed here.

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?

The input schema is minimal: a single 'lessons' array with additionalProperties:true and no item-level structure, so schema description coverage is 0%. The description compensates fully by specifying required fields, type-dependent content fields, constraints, and optional fields, giving the agent everything needed to construct valid payloads.

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 clearly states the verb ('Create') and resource ('lessons'), and explicitly identifies this as a BATCH operation. It distinguishes itself from sibling tools like list_lessons, get_lesson, and update_lessons by framing the batch nature and creation focus.

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 explicit usage context: pass a list even for a single lesson, required fields per lesson, type-specific content requirements, and behavior when omitting optional fields. It does not explicitly name alternatives or exclusion conditions, but the batch emphasis and write scope make the intended use clear.

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