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

Annotations already cover readOnlyHint, destructiveHint and openWorldHint, so the description's burden is lighter. It still contributes real behavioral information beyond them: the result set is silently filtered to 'active online' courses (not all courses), and the response contains only id, name and a count rather than full course objects. It says nothing about pagination or result limits for a parameterless list call.

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 front-loaded sentence that states scope, return fields and count with no filler. The trailing raw endpoint 'GET /courses/list/' adds little for an agent but is minor.

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 zero-parameter, non-mutating list tool with no output schema, the description supplies the two things an agent needs: what subset of courses is returned and what fields come back. The only real gap is pagination/size behavior, which matters if the course catalog is large.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly introduces no parameter concepts and instead describes the fixed output fields, leaving nothing ambiguous about inputs.

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 (list courses) and adds the scope and payload ('active online courses (id and name), plus the count'), which an agent could not infer from the name alone. It does not explicitly differentiate itself from close siblings like axislms_count_courses or axislms_get_course, so it falls short of a 5.

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?

There is no statement of when to use this versus axislms_count_courses (which also returns a count) or axislms_get_course for a single course. Usage is only implied by the word 'List'; no prerequisites or exclusions are given.

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