get_pageFetches any itseasy.co page (e.g. /pricing, /faq, /developers, /legal/tos) rendered as markdown with title/description frontmatter. Paths come from list_pages.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Site-relative page path from list_pages, e.g. /pricing |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already indicates a safe read, and the description adds the output format (markdown with frontmatter) and the dependency on list_pages. This goes beyond the annotation by describing what the response looks like and what prior call is needed.
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 sentences, front-loaded with the action and examples, and the second sentence adds the essential dependency on list_pages. There is no redundancy or filler.
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 one-parameter read-only tool with no output schema, the description covers what is fetched, the markdown format, and how to obtain a valid path. It omits error-handling behavior, but that is not critical for correct invocation.
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 schema already documents the path parameter with an example (/pricing), and the description reinforces that paths come from list_pages while adding more example paths like /faq and /developers. With 100% schema coverage, the description provides only marginal additional meaning, so baseline 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 description clearly states the tool fetches any itseasy.co page as markdown with title/description frontmatter, and provides concrete path examples. It also differentiates from siblings by noting paths come from list_pages and by covering all pages rather than a subset like get_pricing_rates.
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 tells the agent that paths must come from list_pages, implying a required precursor call. It does not explicitly name alternatives or state when not to use this tool, but the scope and examples make the intended context clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
get_page and get_pricing_rates both touch pricing content, but one returns rendered page markdown and the other returns structured JSON, so their purposes are mostly clear. list_pages is distinctly the discovery tool for page paths.
All tool names follow a consistent verb_noun snake_case pattern: get_page, get_pricing_rates, list_pages. The verbs 'get' and 'list' are used predictably for their respective actions.
Three tools is well-scoped for a simple website content and pricing retrieval server. Each tool has a clear role: discover pages, read a page, and fetch structured pricing.
The server covers its apparent domain completely: list_pages provides the page index, get_page retrieves any page, and get_pricing_rates exposes structured pricing data. No major dead ends or missing operations for the stated scope.