get_page_details

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

Annotations already declare readOnlyHint: true, so the description's 'Get' aligns with read-only behavior. However, the description adds no further behavioral context (e.g., permissions, performance, or what 'detailed information' entails beyond the schema).

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 sentence plus a concise Args block. It is front-loaded with the main purpose. The Args block is somewhat redundant with the schema but adds explanatory value, so no wasted words.

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?

The tool has 2 required parameters and an output schema, but the description does not clarify what 'detailed information' covers (e.g., whether it includes page body, settings, etc.) compared to sibling get_page_content. Given the output schema exists, this is adequate but leaves ambiguity.

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?

The description includes an Args section that explains both parameters: 'course_identifier: Course code or Canvas ID' and 'page_url_or_id: Page URL slug or page ID'. Since the schema has 0% description coverage, this adds meaningful semantics beyond the schema's types and 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 'Get detailed information about a specific page', which is a specific verb+resource. It distinguishes from sibling tools like list_pages (listing) and get_page_content (content retrieval), as 'details' implies comprehensive information.

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 description provides no guidance on when to use this tool versus alternatives like get_page_content or list_pages. No exclusions or context are given, leaving the agent to infer without help.

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