Update lesson

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

Adds rich behavioral context beyond annotations: partial updates (fields left out stay), body replacement semantics, that members who completed the lesson keep their completion status, admin-only access, and that the operation runs without confirmation and notifies nobody. This far exceeds the minimal hints from annotations.

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?

Mostly front-loaded and efficient, but redundantly states 'Admins only' twice and uses slightly awkward phrasing ('as its Edit does'). Every sentence carries information, but the duplication is minor waste.

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 mutation tool with full schema coverage and no output schema, the description is complete: it covers authorization, partial update semantics, side effects on completions, and the lack of confirmation/notification. An agent has all needed context to call it correctly.

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?

With 100% schema coverage, baseline is 3, but the description adds meaningful detail: it clarifies that omitted fields remain unchanged and that body replaces the entire text, which is not fully captured by the schema descriptions. It also groups the three editable fields (title, text, video link) in the opening sentence.

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 (Change) and resource (lesson's title, text or video link), and clarifies it edits one lesson page. However, it does not differentiate from siblings like update_post or create_lesson, leaving the agent to infer that this is the lesson-specific update tool.

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?

Provides some usage context (Admins only, edits one lesson page) but gives no explicit guidance on when to use this tool versus alternatives such as get_lesson or create_lesson. No when-not or alternative tool is mentioned.

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