Get a page body as Markdown

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

With no annotations provided, the description carries the behavioral burden. It explicitly states the operation is read-only and specifies the output format (Markdown), which is meaningful context. It does not cover error behavior, but for a simple read-only retrieval the key behavioral traits are disclosed.

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 two concise sentences with no filler. The core action and return format are front-loaded, and the input modes and read-only nature are stated efficiently in the second sentence.

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 tool with two fully documented parameters, the description provides everything an agent needs: what it returns, what inputs it accepts, and its safety profile. No output schema exists, so the explicit 'Markdown' return format is especially valuable and 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 description coverage is 100%, so the schema already fully documents both parameters. The description's statement that it accepts a page title or view id largely restates the page parameter description, adding minimal semantic value beyond the structured 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?

The description uses a specific verb and resource: it returns a document page's body rendered as Markdown. This clearly differentiates get_page from the sibling tools list_pages, search_pages, and list_workspaces, and the mention of view ids from list_pages reinforces the intended scope.

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 implies usage: use it when you need a page's body as Markdown, especially after obtaining a view id from list_pages. However, it does not explicitly state when to avoid it or name alternative tools for other retrieval needs, leaving the routing partly to inference.

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