get_guideRetrieve one canonical Homechecker guide by slug. Use a slug returned by list_guides or search_guides. Returns source links, review metadata, method and limitations with the guide.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Guide slug, for example reading-a-section-32. Use guides for the main hub. | |
| format | No | full | |
| sectionIds | No | When format is sections, return only these section IDs. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. The description adds useful detail about the return value (source links, review metadata, method, limitations) without contradicting annotations.
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 with the main action front-loaded. Every word serves a purpose; no redundancy.
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?
As a read-only retrieval tool with no output schema, the description adequately covers the return content. It could mention error handling for missing slugs, but overall it's 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 67%, and the description adds value for the slug parameter by clarifying its source. However, it does not expand on the format or sectionIds parameters beyond what the schema provides.
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 'retrieve' and identifies the resource as 'one canonical Homechecker guide by slug'. It clearly distinguishes from sibling tools like list_guides and search_guides which return multiple guides.
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?
It explicitly advises to use a slug from list_guides or search_guides, providing clear context. However, it does not explicitly state when not to use this tool, such as for browsing multiple guides.
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.
Each tool has a clearly distinct purpose: list_guides for filtered catalog browsing, search_guides for natural-language queries, get_guide for direct slug-based retrieval, and build_buyer_checklist for constructing a checklist from the corpus. There is no meaningful overlap that would confuse an agent.
All tool names follow the same verb_noun pattern: build_buyer_checklist, get_guide, list_guides, search_guides. The verbs are imperative and consistent, making the naming scheme predictable and easy to infer.
Four tools is well-scoped for a guide-focused server. Each tool covers a distinct operation without redundancy, and the count is neither excessively large nor too sparse for the stated purpose.
The tool surface fully covers the apparent domain: browsing the catalog (list_guides), searching content (search_guides), retrieving a specific guide (get_guide), and synthesizing guides into a checklist (build_buyer_checklist). No obvious gaps or dead ends exist for typical homebuyer guidance workflows.