get_lesson

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

With no annotations, the description must fully disclose behavior. It implies read-only access but fails to mention authentication needs, rate limits, or what 'content and metadata' specifically includes. The output schema exists but is not described, leaving the agent uncertain about return structure.

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 short and front-loaded, but it is too brief to fully inform the agent. Every sentence is necessary but insufficient; there is no wasted text, but the lack of additional context reduces effectiveness.

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 tool has an output schema and multiple sibling tools, the description is incomplete. It does not summarize return fields, error scenarios, or prerequisites. The agent would need to rely on the output schema alone, which is not elaborated.

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 description adds minimal meaning beyond the schema: it restates 'lesson' as 'The lesson name'. Since schema description coverage is 0%, this provides some clarification but is still vague and lacks details like format, uniqueness, or expected values.

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 'Get a lesson with its content and metadata', specifying the verb and resource. It distinguishes from sibling tools like create_lesson, update_lesson, delete_lesson, but does not differentiate from other getter tools (e.g., get_chapter, get_course).

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 guidance is provided on when to use this tool versus alternatives, such as when to use get_chapter or list_cached_courses. There are no prerequisites, exclusions, or hints about preferred contexts.

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