get_page

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

With no annotations, the description must disclose behavior. It adds that the result includes rendered HTML and a preview_url, which are not schema properties. It implies a read-only operation. Could be improved by explicitly stating idempotency or permissions, but still informative.

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 concise sentences, no redundant information. Key details are front-loaded: what the tool does and how to use it.

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 tool with an output schema, the description is complete. It covers the purpose, parameter usage, and key return fields (rendered HTML, preview_url). No missing critical behavior.

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 description compensates. It clarifies that page_id and slug are alternative identifiers and that one should be provided. This adds meaning beyond the schema, which only shows types and null defaults.

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 the tool reads a single page by id or slug, including rendered HTML. The verb 'read' and resource 'page' are specific, and the method (by id or slug) distinguishes it from related tools like list_pages or create_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?

The description explicitly says to provide either page_id or slug, guiding parameter selection. It implies usage for reading a specific page. However, it does not explicitly state when not to use this tool or mention alternatives like list_pages for discovery.

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