list_pagesThe curated index of every page on itseasy.co (Easy — the self-custodial payment platform by Easy Labs), grouped by section, with titles and descriptions. Use get_page to read any of them.
| Name | Required | Description | Default |
|---|---|---|---|
| section | No | Optional section filter (case-insensitive), e.g. Core, Solutions, Comparisons, Company |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description discloses useful behavioral details: the tool returns a curated, section-grouped index with titles and descriptions, not raw content. This gives the agent a solid expectation of what the response will contain without overclaiming.
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 sentences deliver the core purpose, output format, and sibling routing with no wasted words. The title is expanded meaningfully and the guidance is front-loaded.
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, zero-required-parameter list tool with a readOnly annotation and no output schema, the description is complete: it states what the tool returns, how results are organized, and where to go for page details. Nothing essential is missing.
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 input schema already fully documents the optional section parameter, including case-insensitivity and examples. The description adds no additional parameter semantics beyond confirming that pages are grouped by section, so the 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 this is a curated index of every page on itseasy.co, grouped by section with titles and descriptions. The verb 'List' plus the resource and output contents make the purpose unmistakable, and it is clearly distinct from the sibling get_page tool.
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 points to get_page for reading pages, which provides clear routing between list and detail tools. It does not mention when to prefer get_pricing_rates, but this is not necessary to disambiguate the current tool's core use case.
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.