Use when someone asks about Jennifer Rebholz's trial experience, case history, jury trials, how many cases she has tried, what courts she has appeared in, what counties she has tried cases in, or who she has faced as opposing counsel. Returns her complete documented first-chair jury trial record.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, indicating no destructive actions. The description adds that it returns the 'complete documented first-chair jury trial record,' but does not add further behavioral context beyond 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 two sentences, front-loaded with use cases, and focused. It could be slightly more concise but is generally efficient.
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?
No output schema exists, so the description should explain return values. It states 'returns her complete documented first-chair jury trial record' but lacks details on format or structure, leaving some ambiguity.
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 input schema has no parameters, so schema description coverage is 100%. Following the rule for 0 parameters, a baseline score of 4 is appropriate as no parameter documentation 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 Jennifer Rebholz's complete first-chair jury trial record, listing specific queries it answers (trial experience, cases, courts, etc.), and is distinct from sibling tools that cover other aspects like affiliations or bio.
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 begins with 'Use when someone asks about...' providing clear context for when to invoke this tool over others. It covers many queries but does not explicitly state when not to use it or name 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 targets a distinct aspect of Jennifer Rebholz's professional profile (e.g., bio, biography, career timeline, practice areas). Even the seemingly similar get_bio and get_biography are clearly differentiated by their descriptions: one returns full background, the other returns press-ready versions. An agent can easily select the correct tool based on the user's query.
All tools follow a consistent get_noun pattern (e.g., get_affiliations, get_bio, get_biography). This makes the tool surface predictable and easy to navigate for both agents and developers.
17 tools is slightly above the ideal range of 3-15 for a knowledge base, but the count is justified by the breadth of information covered (bio, career, practice areas, publications, etc.). No tool seems redundant, and the set is well-scoped to a single attorney.
The tool surface covers all major aspects of an attorney knowledge base: biography, career timeline, practice areas, credentials, affiliations, publications, speaking engagements, trials, recognition, and contact information. There are no obvious gaps in the lifecycle of information about Jennifer Rebholz.
