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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: the return format, compatibility with create_lesson, and the legacy empty-document behavior. This is useful, though it does not discuss errors or availability.

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: it leads with the return format, then the relationship to create_lesson, then the edge case. Every sentence earns its place and no information is redundant.

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 simple one-parameter read-only tool with no output schema, the description is complete enough. It tells the agent what data will be returned, which block types to expect, how to use the result with create_lesson, and what to expect for older lessons. No critical information is missing.

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%, so the description carries the burden of parameter explanation, but it does not explicitly discuss lesson_id. However, the single parameter is self-explanatory from its name and type, so the lack of description is not a serious obstacle. It adds no extra parameter semantics, but none are really needed here.

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 identifies the resource (lesson) and the format (Editor.js blocks), and names the specific block types returned. It also distinguishes the tool from siblings by noting that the response can serve as a template for create_lesson, making its purpose and scope immediately clear.

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 an explicit use case: the response is suitable as a sample for create_lesson. It also explains the old-lesson edge case where the document may be empty and content lives in blocks. It does not enumerate exclusions or alternatives like update_lesson, but the guidance is sufficient for a read-only retrieval tool.

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