canvas_get_page

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

No annotations are provided, so the description carries the full burden. It does disclose two useful traits: the body is returned as plain text (not HTML) and max_chars bounds the payload with 0 meaning the server default. However, it says nothing about auth requirements, whether missing pages error or return empty, or whether the content is truncated silently.

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?

One sentence of purpose followed by a tight per-argument list. No filler, and the essential return-format fact is front-loaded.

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 an output schema present, return values need limited explanation, and the three parameters are all documented. The remaining gap is behavioral rather than structural: truncation semantics for max_chars and failure behavior for an invalid slug are unstated on a tool with no annotations to fall back on.

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 compensate, and it does: page_url is defined as a url slug plus its source tool, course_id is a numeric id with its default env var named, and max_chars is defined as a payload bound where 0 selects the server default. All three parameters gain meaning beyond the bare schema.

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 ('Get one wiki page's body') and specifies the return format ('as plain text'), which immediately distinguishes it from canvas_list_pages, canvas_create_page, and canvas_update_page. An agent can identify the operation without opening the schema.

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 parenthetical '(from canvas_list_pages)' establishes an explicit upstream workflow for obtaining the page_url, which is real routing guidance. It gives no exclusions or when-not conditions, but the context for correct use is clear enough.

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