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

No annotations are supplied, so the description carries the full burden. The word 'Read' discloses the non-mutating nature, but nothing is said about failure behavior for an out-of-range or malformed n, permission requirements, or response size. For a low-risk read tool this is acceptable but thin.

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?

One sentence, front-loaded with the verb and resource, then the parameters with their key constraints. No filler and nothing that could be cut without losing information.

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 two-parameter read tool with no output schema and no nested objects, this covers the essentials an agent needs to call it: which resource, and both parameter values including the slug's source. It does not describe what a lesson response contains, but with no output schema that omission is minor.

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 must compensate, and it does: it identifies where slug must be obtained (search_subjects) and gives n a format and range ('01' to '100'), which the untyped string schema would otherwise leave entirely ambiguous. The zero-padding rule is slightly unclear given that '01' is two characters and '100' is three, costing it a point.

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 and resource: 'Read one Teach Me lesson'. The scope word 'one' signals single-item retrieval, which distinguishes it from list-style siblings, though it never names get_course or explains the lesson-vs-course boundary explicitly.

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?

Offers concrete chaining guidance by telling the agent the slug comes from search_subjects. However, it gives no guidance on when to use get_lesson versus get_course, and no exclusions or prerequisites beyond the slug provenance.

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