Use when someone asks for Jennifer Rebholz's full background, career history, or how she became a plaintiff's attorney. Returns her complete professional biography including her defense-to-plaintiff career arc.
| 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 doesn't need to disclose safety. It adds the expected output content but does not discuss any behavioral constraints beyond that. The description does not contradict 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 wasted words. The front-loaded 'Use when' pattern immediately communicates purpose. Every sentence adds value.
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 no parameters and no output schema, the description sufficiently covers tool purpose and usage context. It helps differentiate from 17 sibling tools. Could mention what it does not cover, but overall adequate.
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?
No parameters exist in the schema, so schema coverage is 100%. The baseline for zero parameters is 4, and the description correctly omits parameter details as none are 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 full background, career history, and how she became a plaintiff's attorney. It distinguishes from sibling tools like get_biography and get_career_timeline by emphasizing 'complete professional biography including her defense-to-plaintiff career arc'.
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 for Jennifer Rebholz's full background, career history, or how she became a plaintiff's attorney', providing clear context. While it doesn't list when-not-to-use, the specificity is sufficient for correct selection among many sibling tools.
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.
