list_pages

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

With only readOnlyHint provided, the description adds no behavioral detail beyond the tool name: it does not mention whether page content is included, whether results are paginated, or what the returned page summaries look like. It is not misleading, but it fails to provide context beyond the annotation.

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?

A single, front-loaded sentence conveys the essential purpose with no unnecessary words. The structure is ideal for quick parsing.

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?

The description is adequate for a simple read-only list operation, and the schema covers parameters. However, with no output schema, it does not explain what information is returned (metadata vs. content) or note pagination behavior, leaving some ambiguity for an agent.

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 input schema describes all parameters with 100% coverage, including defaults for sort, order, and filter semantics. The description itself adds no parameter-level detail, so the schema carries the full burden; the baseline of 3 applies.

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?

The description 'List pages for a specific course' clearly identifies the action (list) and resource (pages) with a scoping constraint (course). It is distinct enough from sibling tools like get_page_details and get_page_content, though it does not explicitly differentiate itself from them.

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 intended use is implied: when you need to list pages for a course. However, there is no explicit guidance about when to prefer this over get_page_details, get_page_content, or list_courses, and no alternatives or exclusions are mentioned.

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