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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only paging behavior ("Page with offset") and the do-not-guess caution; it says nothing about result ordering, page size, or total counts.

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 short sentences with no filler, and the highest-value instruction (find the user's programs before acting) is front-loaded. Could be marginally tighter by merging the ID caution with the paging sentence, but nothing is wasted.

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 one-parameter read that returns structured data covered by an output schema, the description supplies the essential context: when to call it, how to page, and how to use the returned IDs. Minor gap is lack of guidance on how offset interacts with result volume.

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 description coverage is 0% for the single offset parameter, so the description must carry meaning: "Page with offset" is the only hint it gives. It conveys the pagination intent but not page-size semantics, what offset counts, or how to detect the end of the list.

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+resource: retrieving the user's saved curriculum programs, with the scope word "saved" narrowing it. It reads slightly as a lookup ("Find") rather than a paged list, but the intent is unambiguous and distinguishable from sibling reads like search_curriculum or get_curriculum_context.

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 clear timing guidance ("before answering or editing") and an operational rule ("Use the returned ID; do not guess programs"), which is exactly the workflow context an agent needs. It does not name an alternative tool or a when-not condition, so it stops 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.