LessonPackagesWriteOffLessons

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

Annotations already mark the tool as destructive, and the description adds useful specifics: it decrements lesson balance and requires client-side approval. This goes beyond the structured hints, though the mechanics of client-side approval are not elaborated.

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 compact and front-loaded: one sentence states the core action, and the warning follows immediately. Every sentence earns its place with no 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?

For a destructive mutation with 5 required parameters, the description captures the essential effect and approval requirement, while parameter semantics are fully covered by the schema. The lack of an output schema makes omitting return-value details less critical, though the approval flow remains somewhat vague.

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?

All 5 parameters have schema descriptions, so the baseline is 3. The description does not add parameter-level detail, though 'decrements lesson balance' indirectly clarifies the meaning of bodyCount.

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 phrase 'Write off lessons from a package' states a specific verb and resource, immediately distinguishing this from siblings like LessonPackagesGetList, LessonPackagesSetPackage, and LessonPackagesUpdatePackagePeriod. The action 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?

Usage is implied by the action name: use this when lessons need to be decremented from a package. The warning adds an important prerequisite of client-side approval, but no explicit alternatives or when-not-to-use guidance are provided.

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