get_crisis_resourcesReturn the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint: true. The description adds that the payload is 'canonical' and suggests it should be surfaced with urgency, which is useful behavioral context beyond the annotation. No contradictions with the read-only annotation.
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, no redundant words. The first sentence states the function and the second gives usage guidance. Perfectly sized and 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 tool with no parameters, no output schema, and a straightforward read-only action, the description fully covers its purpose, usage trigger, and distinguishes it from all siblings. It is complete.
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 mentions no parameters, but none exist to document, so no additional value is needed.
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 a specific verb ('Return') and resource ('canonical 988 / 911 / Crisis Text Line payload'). It distinguishes itself from siblings that handle articles/microsite info, making the purpose unambiguous.
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?
Explicitly states when to use: 'immediately whenever the user signals self-harm or imminent danger.' This is a clear trigger condition. Since no alternative tool exists for this purpose (siblings are about articles), no exclusions are necessary.
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: fetching a single article, listing articles, searching articles, citing, crisis resources, and site info. No two tools could be easily confused, even list and search are differentiated by query vs. pagination.
All tool names follow a consistent verb_noun pattern (cite_article, get_article, list_articles, search_articles, etc.). The convention is uniform and predictable.
With 6 tools, the set is well-scoped for an article library, covering reading, searching, listing, citing, plus crisis and site info. No redundancy or bloat.
The tool surface covers the core library workflow: discover (list/search), access (get), cite, and contextual info (microsite). The inclusion of crisis resources is a thoughtful addition for the domain. No obvious gaps for a read-only content library.