find_peopleSearch for people by matching every query word across a family tree or the shared collection. Use results to reuse existing UUIDs before creating new people.
Find names matching every query word. Omit tree to search the shared collection.
Search globally before creating people; reuse existing UUIDs with set_tree_members.
| Name | Required | Description | Default |
|---|---|---|---|
| tree | No | ||
| query | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While the annotations cover the safety profile (readOnly), the description adds crucial operational behavioral traits, such as the matching logic ('matching every query word') and defining the tool's role as a discovery step, which is vital 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?
The two sentences are highly dense with information, providing clear definitions of scope and workflow in a front-loaded, efficient manner.
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 complexity of the ecosystem (multiple tree and people manipulation tools), this description provides all necessary context for the agent to decide when to use this lookup function versus mutation tools like 'set_tree_members'.
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?
Since schema description coverage is 0%, the description must compensate. It successfully explains the intended use of 'tree' (scoping the search) and how to execute a global search (omitting it). It also defines the matching mechanism based on the 'query'.
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 defines the core action ('Find names matching') and immediately differentiates its scope: it searches globally ('shared collection') unless a specific tree is omitted.
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?
It provides explicit workflow advice by stating 'Search globally before creating people' and gives a clear pathway for subsequent actions by mentioning the related tool, 'set_tree_members'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.