Use when someone asks what colleagues, opposing counsel, or peers say about Jennifer Rebholz, her reputation in the legal community, her AV Preeminent rating, or peer reviews of her work. Returns verified attorney peer reviews from Martindale-Hubbell.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the description adds minimal behavioral insight beyond confirming it returns reviews. The source (Martindale-Hubbell) is useful context.
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 focused sentences, front-loaded with usage context, no wasted words.
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 no-parameter read-only tool, the description adequately explains return content. Missing mention of result format or any limitations, but not critical given simplicity.
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?
With no parameters and 100% schema coverage, baseline is 3. The description adds meaning by describing the output, but no parameter-specific guidance 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 verified attorney peer reviews from Martindale-Hubbell, with specific use cases (reputation, AV Preeminent rating). This distinguishes it from sibling tools like get_bio or get_credentials.
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 says 'Use when someone asks...' providing clear context. However, it does not mention when not to use or alternative tools for related but distinct queries.
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.
