get_page_details

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

Beyond the readOnlyHint annotation, the description discloses the 500-character cap, that the preview drops all markup, and — critically — that embedded media is listed separately rather than silently disappearing. These edge-case disclosures add real behavioral context that the annotation does not provide.

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?

Two short paragraphs with front-loaded purpose. The first sentence states the main action, and the second paragraph adds only high-value details: returns, the 500-character cap, markup-stripping, media handling, and the alternative tool. 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?

With no output schema, the description carries the burden of explaining return values and does so thoroughly — it enumerates the metadata fields (status, timestamps, editor, editing roles), describes the preview format and cap, and handles the media edge case. For a two-parameter tool with a readOnly annotation, this is fully self-sufficient.

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 100%, with both page_url_or_id ("Page URL slug or page ID") and course_identifier ("Course code or Canvas ID") fully documented. The description adds no meaningful parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 opening sentence "Get a specific page's metadata plus a short text preview" uses a specific verb and resource, and "specific page" distinguishes it from list_pages. The closing sentence explicitly names get_page_content as the alternative for full content, further differentiating it from its closest sibling.

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 explicitly states when to use this tool (when metadata plus a plain-text preview is needed) and when not to: "For the full body, including media markup, use get_page_content." This is a clear, named alternative with no ambiguity.

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