get_policyRetrieve any Sunleaf store policy—shipping, returns, privacy, or wholesale—as Markdown to answer customer questions accurately.
The full text of one Sunleaf store policy as Markdown: shipping, returns, privacy or wholesale.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Which policy to read |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the Markdown output format detail, which is useful but minimal additional context. No contradiction with 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?
A single front-loaded sentence with zero filler. The core purpose, format, and available options are packed efficiently without 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?
For a simple single-parameter read tool with full schema coverage and comprehensive annotations, the description is nearly complete. It specifies the output format and available values; the only gap is behavior for invalid input, which the enum constraint largely mitigates.
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 100%, with the single 'name' parameter fully documented via its enum and description. The description's list of policies (shipping, returns, privacy, wholesale) mirrors the enum values, adding little beyond what the schema already provides. 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?
States a specific resource (Sunleaf store policy), the deliverable (full text as Markdown), and enumerates the four available policies. This clearly distinguishes it from siblings like search_faqs and search_products, which retrieve different content types.
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 for policy text retrieval by listing the policy names, but offers no explicit when-to-use vs. alternatives guidance. It does not reference siblings or state exclusions, though the enumerated policy list narrows scope effectively.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.