get_microsite_infoIdentity and links for Therapy for Teens: tagline, audience, focus, publisher, sponsor relationship to Emora Health, and key URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already declares this is a safe read operation. The description adds no additional behavioral context, but for a simple info retrieval tool, this is acceptable and does not contradict the 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?
The description is a single, well-structured sentence that front-loads the purpose and lists specific content areas without any extraneous information.
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?
The description provides a thorough list of content areas and is sufficient for a tool with no parameters and no output schema. It clearly conveys what the agent can expect to receive, though it stops short of describing the exact return format.
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?
There are zero parameters, so the description has no parameter documentation burden. The baseline of 4 applies because the schema is empty and no explanation 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 the tool returns identity and links for the Therapy for Teens microsite, listing specific content categories (tagline, audience, focus, publisher, sponsor relationship, URLs). This distinguishes it from sibling tools that handle articles and crisis 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?
No guidance is provided on when to use this tool versus the sibling tools. The description only lists what it returns, with no mention of alternatives or exclusions, leaving the agent to infer its purpose.
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 serves a distinct purpose: fetching a single article, listing articles, searching, citing, retrieving crisis resources, and getting site info. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern (cite_article, get_article, list_articles, search_articles, etc.). The verbs accurately describe the action and the nouns are clear.
Six tools is appropriate for a read-only content library. Each tool covers a necessary functionality (list, search, get, cite, plus safety and context) without unnecessary bloat or missing essentials.
The tool surface fully covers the core domain of accessing articles: listing, searching, retrieving, and citing. The addition of crisis resources and microsite info completes the lifecycle for a safe, well-rounded library. No obvious gaps.