Return a concise, reviewed orientation to the Lipe case with evidence classifications and page citations. Use for first-time users, then search and fetch before answering detailed questions.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| case | Yes | ||
| type | Yes | ||
| sections | Yes | ||
| limitations | Yes | ||
| schema_version | Yes | ||
| last_reviewed_at | Yes | ||
| authoritative_next_step | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context: the result is concise, reviewed, and includes evidence classifications and page citations. No contradiction with annotations.
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 with no filler. The first sentence states exactly what is returned and the second gives usage guidance. Every clause earns its place, and the most critical identifying information is 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 zero-parameter, read-only overview tool with an output schema present, the description is fully sufficient. It names the case, the content delivered, the intended audience, and the recommended follow-up actions. Nothing needed to invoke it correctly 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?
The tool has zero parameters, so the schema places no burden on the agent. The description appropriately adds no parameter details because none exist, and the baseline for a zero-parameter tool is 4.
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?
States a specific verb ('Return') and a distinct resource ('a concise, reviewed orientation to the Lipe case with evidence classifications and page citations'). It clearly differentiates from sibling tools by positioning itself as the orientation entry point rather than a search, fetch, or topic-listing tool.
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 directs when to use it: 'Use for first-time users, then search and fetch before answering detailed questions.' This provides both the trigger condition and the recommended follow-up sequence, leaving no ambiguity about its role relative to alternatives.
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 role: search queries the corpus, fetch retrieves a specific result page, get_case_overview provides the summary, and list_case_topics enumerates available topics. No two tools overlap in purpose or output.
Names are all lowercase imperative verbs, and multi-word tools use underscore-separated verb_noun format. The single-word names fetch and search are slightly less descriptive than the get_/list_ prefixed names, but the style is otherwise consistent.
Four tools is well-scoped for a read-only court-record connector: an orientation tool, a topic list, a search operation, and a page-fetch tool. Each tool serves a necessary function without redundancy.
The set covers the full workflow from orientation and topic discovery to search and exact-page retrieval with provenance and citation. No obvious missing operations for the stated purpose of answering questions from the Lipe record.