get_crisis_resourcesCanonical crisis-resource payload (911, 988 Suicide & Crisis Lifeline, Crisis Text Line). Hardcoded — overrides any other tool when high-severity language is detected.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description discloses that the payload is hardcoded (static) and that the tool overrides other tools under specific conditions. This adds significant behavioral context, informing the agent that this is a deterministic, high-priority fallback.
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 a single front-loaded sentence that conveys purpose, content, and behavioral override in an extremely concise manner. Every word earns its place, with no redundant phrasing 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?
Given the tool's simplicity (zero parameters, read-only annotation, no output schema), the description is complete. It tells the agent what the tool returns, when to invoke it, and how it behaves in relation to other tools. No additional information is needed for correct selection and 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 tool has zero parameters, so the description carries no parameter burden. The description adds context by listing the included resources (911, 988, Crisis Text Line), which is useful semantic information beyond the empty schema. Baseline is 4 for no-parameter tools.
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 identifies the tool as providing the canonical crisis-resource payload (911, 988, Crisis Text Line) and explicitly states it overrides other tools when high-severity language is detected. This distinguishes it from sibling tools like book_appointment or search_content, which serve unrelated purposes.
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 states when to use this tool: when high-severity language is detected. It also clarifies that it overrides any other tool, providing a clear decision rule for the agent. No alternative tools are mentioned, but the override condition is a strong usage guideline.
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 targets a distinct action (about, book, browse, check, find, search, start) and descriptions clarify boundary cases (e.g., book_appointment vs book_matching_session, search_content vs browse_pages). Minor overlap remains between about_emora's service catalog and browse_pages' service/specialty/insurance pages, but it is unlikely to misdirect an agent.
Tool names are uniformly lowercase snake_case and mostly follow an imperative verb_noun pattern (find_provider, check_availability, get_cost_estimate). Two small deviations — about_emora and start_here — are still readable and don't undermine the overall predictable pattern.
Ten tools is squarely in the ideal range and each one serves a meaningful step in the mental-health care journey: orientation, crisis support, content search, provider matching, availability, cost estimation, and booking. There is no obvious redundancy or bloat.
The tool set covers the full discovery-to-booking funnel, including crisis triage, provider search, availability, cost estimates, and two booking paths. Minor gaps exist (no explicit reschedule/cancel or appointment-list tool), but those actions plausibly live outside this server's hand-off model.