canvas_list_pages

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

No annotations are provided, so the description carries the burden. It discloses a real behavioral trait beyond the schema: that the returned `url` is the slug the other page tools consume, not page_id or a full URL. It still doesn't state pagination behavior or permissions, but output schema exists to cover returns.

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 tight lead sentence that front-loads purpose and payload scope, followed by the single most important caveat (the url vs page_id trap). Every sentence earns its place.

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 two-param read tool with an output schema, the description covers purpose, both parameters, and the critical returned-field gotcha. Only explicit sibling routing and pagination semantics are absent.

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%, so the description must compensate, and it does: course_id is a numeric id defaulting to CANVAS_DEFAULT_COURSE_ID, and search_term is a title substring filter. This exceeds what the bare schema provides.

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+resource ('List wiki pages in a course') and immediately scopes the payload ('titles and url slugs, not bodies'). This distinguishes it from canvas_get_page, which fetches a body.

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?

Clear context (course-scoped wiki page listing) with the 'not bodies' exclusion implying the agent should use get_page for content. It does not explicitly name canvas_get_page as the alternative, so it falls short of a full 5.

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