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

Annotations already declare it a safe read (readOnlyHint, destructiveHint false), and the description adds real context on top: PII sensitivity ('Contains personal data') and pagination behavior ('paged, 100 per page'). The endpoint path is a useful bonus, though return shape and rate-limit behavior remain undisclosed.

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 tight sentences, front-loaded with the core resource before enumerating kinds and constraints. The trailing endpoint path is slightly technical filler but doesn't bloat the text.

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 six-param read tool with annotations but no output schema, the description covers the essential dimensions: what kinds exist, scope mechanics, pagination, and PII sensitivity. count_only and page are left to the schema, which documents them adequately, so nothing critical is missing.

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?

With 83% schema coverage the baseline is 3, but the description genuinely adds meaning by glossing each kind ('courses (status, progress, score, dates)', 'archived (archived and imported course results)') and mapping the scope values to user/all/filtered intent. That extra semantics lifts it above the schema-only baseline.

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 resource (a learner's records across the LMS) and enumerates the five kinds plus the three scopes, so an agent knows exactly what it retrieves. It doesn't explicitly name which sibling report tool to prefer (certification_report, course_report), leaving that differentiation implicit.

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?

The scope enumeration ('for one user, for all users, or for users matching a search phrase') implies when each mode applies, and the schema backs it with scope descriptions. But there's no explicit guidance on when to pick this over the sibling axislms_certification_report / axislms_course_report tools, so usage stays inferred rather than stated.

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