cite_articleGet a formatted citation for a Psychiatry for Teens article. Supports AMA, APA, and Chicago styles.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Article slug. | |
| format | No | Citation style (default ama). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include readOnlyHint: true, so the description need not repeat safety traits. It adds useful context about supported citation styles, which informs the agent of the tool's capabilities. It does not mention error behavior or return formatting, but for a read-only citation tool with good annotations, this is adequate.
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 two sentences, front-loaded with the verb 'Get,' and every word contributes meaning. It is concise without sacrificing necessary information about supported styles.
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?
This is a simple tool with two parameters (one required, one defaulted), 100% schema coverage, and a readOnlyHint annotation. The description fully conveys what the tool does and what styles it supports. No output schema exists, but the return value (formatted citation) is clear from the description. Nothing essential is missing.
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 description coverage is 100%, with both parameters (slug and format) documented. The description adds no new semantic detail beyond the schema; it only reiterates the supported styles already present in the enum. Baseline of 3 is appropriate because the schema does the heavy lifting.
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: 'Get a formatted citation for a Psychiatry for Teens article.' It specifies the resource (Psychiatry for Teens article) and the action (get formatted citation), and distinguishes it from sibling tools like get_article by focusing specifically on citation generation.
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 establishes a clear context: it is used for generating citations, with supported styles (AMA, APA, Chicago). It does not explicitly exclude alternatives or name sibling tools, but the purpose is so distinct that the intended usage is clear. No when-not-to-use guidance is given, but it is easy to infer.
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 clearly distinct purpose: article discovery (list, search), retrieval (get), citation (cite), site identity (microsite info), and crisis support. No two tools overlap, and the descriptions reinforce their uniqueness.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., cite_article, list_articles, get_crisis_resources). The naming is uniform and predictable.
Six tools is well-scoped for a read-only article library. It covers discovery, retrieval, citation, site context, and crisis support without unnecessary bloat.
The domain is fully covered: users can search, list, retrieve full articles, generate citations, access site information, and get crisis resources. No critical operations are missing, and the set forms a complete workflow.