canvas_context_page

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

The annotations already declare that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds that the page must be accessible and that page_url comes from the page list, but it does not describe failure behavior or the difference between raw and normal responses.

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 a single front-loaded sentence with no wasted wording. The key action and the required page_url source are both stated immediately.

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 simple read-only page fetch, the description plus annotations and fully documented schema provide enough information to invoke the tool correctly. The only notable gap is that sibling differentiation is left to the agent’s inference.

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 100%, so the schema already fully documents the five parameters. The description only reinforces that page_url comes from the page list, which is largely redundant with the schema’s own parameter description.

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 states a specific verb and resource: read an accessible course or group page. It is clear enough to act on, but it does not distinguish this tool from siblings such as canvas_page, canvas_pages, or canvas_front_page.

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?

It gives a concrete sourcing instruction—use page_url from the page list—and limits scope to accessible course/group pages. However, it does not explain when to choose this tool over canvas_page or canvas_front_page, so usage guidance is only implied.

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