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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral context beyond them: the return format (markdown) and the notable constraint that quiz questions come without answers because learners take the quiz on the site — a detail that prevents an agent from promising answer keys.

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?

Two sentences, front-loaded with the verb and resource, then usage. The content enumeration is long but every listed element (lesson text, quiz, lab) is genuinely distinct information an agent needs to plan around.

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?

With no output schema, the description carries the burden of describing returns, and it does: it lists the payload sections and states "Returns markdown." That is complete enough for a single-parameter read tool; only the error case for an invalid id is unaddressed.

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?

There is a single required parameter with 100% schema description coverage and a 39-value enum, so the schema does the heavy lifting. The description adds no meaning about the id beyond what the enum already conveys, which is the baseline for full-coverage schemas.

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 ("Get one Slop Curriculum module") and enumerates exactly what the payload contains: abilities, lesson text, quiz questions, lab brief and checklist. It is clearly the singular counterpart to list_curriculum, though it never names that sibling explicitly, so the differentiation is inferred from "one" rather than stated.

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?

Gives concrete usage context: "Use to explain a topic from the course or to help someone prepare." That is clear when-to-use guidance, but there is no when-not guidance and no explicit pointer to list_curriculum for discovering valid ids (that pointer lives only in the schema).

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