Get page

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context about output shape: file links appear inline as (file:<id>) and are also listed in file_links, plus a hand-off to canvas_read_file. It says nothing about pagination, truncation of long pages, or errors on bad slugs.

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?

Three short sentences, action first, then parameter sourcing, then output format. No filler and nothing buried at the end.

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?

With no output schema, the description usefully sketches the return payload (text plus inline file references and a file_links list) and points to the follow-up tool. The remaining gap is the undocumented course_id parameter and no mention of error behavior for invalid slugs.

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 coverage is 0%, so the description must carry the load. It explains page_url well, including the 'front_page' sentinel which is a real semantic addition. course_id, however, is never described — the agent must infer it comes from canvas_list_courses — leaving half the parameters undocumented.

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: 'Read a course page as text.' The reference to using the page_url slug from canvas_list_pages/list_modules implicitly separates it from the listing sibling, though it never names an alternative tool for the 'fetch by id' niche explicitly.

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?

Gives concrete guidance on how to obtain the page_url value (from canvas_list_pages or list_modules) and names the 'front_page' sentinel as a valid shortcut. It stops short of stating exclusions or failure conditions, but the routing context is clear.

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