academy_lesson

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

The readOnlyHint already covers the read-only nature, and the description adds useful behavioral context beyond that: the tool returns the full lesson text and is meant to be followed by tutoring, examples, and Q&A. That is sufficient for such a simple fetch operation.

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?

Three concise sentences with no filler. The tool's purpose is front-loaded, and the tutoring-related sentences are useful instructional context rather than redundant prose.

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 read-only lesson-fetch tool, the description is mostly complete: it states what is returned, how to use the content, and when to invoke it. It is slightly lacking in connection to the companion academy_lessons activity, so the overall flow is not fully explicit.

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 no parameter-level meaning about level, slug, or locale. The input schema already documents slug and locale, but level remains just a number 1-6; this description neither clarifies nor compensates for that gap.

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 starts with a clear, specific action: 'Get the FULL text of one lesson.' It identifies the resource, scope, and output shape while distinguishing itself from list-style siblings like academy_lessons.

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?

'This is how a user takes the course with you as tutor' provides an explicit trigger for using the tool, and the teaching instructions clarify the expected interaction flow. It does not name alternatives or when-not-to-use cases, so it falls just short of a 5.

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