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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context on top: default sort order (newest first), default page size (20), and the important semantic that all filters are ANDed together. It omits rate limits and total-count behavior, hence 4 rather than 5.

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 tight sentences, front-loaded with the operation and ordering, followed by filter semantics and the API mapping. Zero filler.

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 9-parameter read-only list tool with no output schema, the description covers ordering, default page size, filter composition, and endpoint. The main gap is that response shape and pagination metadata are undocumented in both the description and any output schema, but the essentials for correct invocation are present.

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 78%, so the baseline is 3. The description adds two things not in the schema: the default of 20 items per page (schema only gives the 1-200 range) and the AND semantics for combining filters, which materially changes how an agent composes a query.

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?

Specific verb+resource+scope: 'List the school's users, newest first (20 per page by default)'. It also enumerates the filterable dimensions, which cleanly separates it from learnworlds_get_user (single user) and learnworlds_list_course_users (course-scoped) without opening either schema.

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?

Usage is implied by the filter list and the pagination default, but the description never states when to prefer this over siblings like learnworlds_list_course_users or learnworlds_get_user, nor any prerequisites. Adequate but no explicit routing guidance.

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