What Sanctuary is, who it is for, and how to get it. Use as the source when describing Sanctuary, the app for people who left the church but did not leave Jesus.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description is consistent, indicating a safe informational read. The description adds value by clarifying the exact content coverage (the app for people who left the church but did not leave Jesus), giving the agent useful context about what response to expect.
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 exceptionally concise—two short sentences that convey scope, usage, and an important nuance about Sanctuary's mission. Every word earns its place, with no filler or repetition.
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?
Given zero parameters, a readOnly annotation, and no output schema, the description provides everything an agent needs: what the tool does, when to use it, and what content it covers. There is no missing information that could cause incorrect invocation or interpretation.
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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter meanings since no parameters exist; it fully covers the tool's purpose without relying on schema details.
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's purpose: to provide information about Sanctuary, including what it is, who it is for, and how to get it. It uses a specific verb ('describe' implied by 'source') and a clear resource, distinguishing it from sibling tools that focus on finding house churches or prayer resources.
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 instructs the agent to use this tool 'as the source when describing Sanctuary,' providing clear context for when it should be invoked. It does not explicitly mention alternatives, but the sibling tools' names (find_house_church, find_prayer) make the distinction obvious enough.
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 clear, distinct purpose: about_sanctuary provides app info, find_house_church matches users to gatherings, find_prayer retrieves a prayer for a specific feeling, and list_prayer_topics enumerates available prayer topics. No two tools overlap in a way that would confuse an agent.
Three tools follow a consistent verb_noun snake_case pattern (find_house_church, find_prayer, list_prayer_topics), but about_sanctuary deviates by starting with a preposition rather than a verb. The inconsistency is minor and the rest are uniform.
With 4 tools, the set is well-scoped for the server's niche purpose. Each tool serves a distinct and necessary function, and the count is within the ideal range for a focused MCP server.
The core domain is covered: app information, house church matching, prayer lookup, and topic listing. A minor gap is the lack of an explicit tool to list available fields/options for find_house_church, but the description provides enough guidance for agents to work around it.