Search the Lipe court record for case facts, testimony, positions, rulings, and jury findings. Call this for every case-specific factual question, then call fetch on relevant result IDs before answering.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive behavior, and the description does not contradict them. It adds behavioral context by indicating that searches return result IDs and that fetch must be called on those IDs before answering, which is useful beyond the structured 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, no filler. The first sentence states the action and scope, and the second provides usage and follow-up guidance. Every sentence earns its place.
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 low complexity, rich annotations, and presence of an output schema, the description is complete enough for correct invocation. It covers what to search, when to call it, and what to do with the results, so an agent can use this tool without needing additional context.
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 schema only defines a required string 'query' with 0% description coverage, so the description must compensate. It does so by specifying what the query searches over—case facts, testimony, positions, rulings, and jury findings—and by framing the query as a case-specific factual question. This adds meaning despite not detailing query syntax.
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 opens with a specific verb and resource: 'Search the Lipe court record for case facts, testimony, positions, rulings, and jury findings.' This clearly defines what the tool does and its scope, and the distinction from overview/topic siblings is implied through the focus on case-specific factual content.
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 gives explicit when-to-use guidance: 'Call this for every case-specific factual question.' It also provides a follow-up workflow with fetch on relevant result IDs. It does not explicitly contrast with get_case_overview or list_case_topics, but the use case is clear enough.
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.