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

Annotations already declare readOnly, idempotent, openWorld and non-destructive. The description adds real operational context on top: the default and maximum page sizes, the contentVersion requirement for paging past page 1, that this is a public endpoint, and that it returns English natural-language text preserving sources, conditions and pagination.

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 dense sentences with the core action front-loaded and paging constraints second. No filler, though the second sentence packs several unrelated facts (public endpoint, language, source preservation) into one run-on.

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 5-parameter, output-schema-less read tool with 20% schema coverage, the description covers pagination well but omits what the 'course' identifier is, what 'packages' contain, and any hint of the return structure beyond 'totals and shared interpretation.' Adequate but with clear gaps.

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 only 20%, so the description must carry weight. It partially does: it explains pageSize bounds, the page>1 contentVersion rule, and the locale's effect via schema. However, the required 'course' parameter (just a 4-char string) and contentVersion format are never explained, leaving the most important input under-defined.

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 complete packaged study plans in study order, with totals') and adds scope details (totals, shared interpretation). It is distinguishable from get_course and get_course_pathways, though it never names a sibling 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?

Provides procedural conditions (default pageSize 5, max 20, page > 1 requires the original contentVersion) that imply usage context, but never says when to choose this over get_course, get_course_pathways or search_courses. Guidance is implied rather than comparative.

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