list_pages

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

Annotations already declare readOnlyHint: true, so the read-only nature is clear. The description adds behavioral context by listing parameters (e.g., sorting, filtering by published status), but does not disclose whether results are paginated or limited. This is adequate given the annotations.

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?

The description is concise: one sentence stating the primary purpose followed by a parameter list. It is front-loaded and avoids fluff. The docstring format is acceptable, though it could be more streamlined.

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?

Given the existence of an output schema and annotations, the description covers the core functionality and parameter details. However, it lacks information about result size limits, pagination, or that it returns page metadata (not full content). This is adequate but not fully complete.

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 0%, but the description provides meaningful explanations for each parameter: 'Course code or Canvas ID' for course_identifier, 'Sort by title, created_at, or updated_at' for sort, 'asc or desc' for order, 'Filter pages containing this term' for search_term, and 'Filter by published status (None for all)'. This adds significant value beyond the schema titles.

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 clearly states 'List pages for a specific course,' specifying the verb (List), resource (pages), and scope (for a course). This distinguishes it from sibling tools like get_page_content (single page) or create_page. The parameter list further clarifies filtering capabilities.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention when not to use it (e.g., for retrieving full page content) or suggest alternative tools like get_page_content or search_canvas_tools.

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