list_peopleRetrieve all people (clients) for the authenticated user. Optionally search by name.
| Name | Required | Description | Default |
|---|---|---|---|
| pace | No | Filter by preferred pace (e.g. quick, measured, deliberate) | |
| tone | No | Filter by tone (e.g. confident, collaborative, analytical) | |
| voice | No | Filter by communication voice (e.g. direct, warm, conversational) | |
| search | No | Search by name (partial match, case-insensitive) | |
| archetype | No | Filter by behavioral archetype |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosure. It states the scope (authenticated user) but fails to mention read-only nature, pagination, ordering, rate limits, or behavior for empty results.
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 a single concise sentence with a clear front-loaded purpose. However, it sacrifices completeness for brevity by not covering the available filters, which is a structural deficiency.
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 five optional parameters, no output schema, and no annotations, the description is insufficient. It does not mention that all filters are optional, return format, pagination, or any behavioral details, leaving major gaps for a list tool.
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?
Schema coverage is 100%, so baseline is 3, but the description only mentions the 'search' parameter and ignores 'pace', 'tone', 'voice', and 'archetype'. This omission is misleading and reduces the value added beyond the schema.
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 retrieves all people for the authenticated user, distinguishing it from single-person retrieval tools like get_person. However, it only mentions search by name, omitting four other filtering parameters, so the purpose is not fully specified.
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?
No guidance is provided on when to use this tool versus alternatives such as get_person for a single person or batch_create_persons for creation. No context or exclusion criteria are given.
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.
Most tools have distinct purposes (create, retrieve, chat). However, generate_compass overlaps with the automatic compass generation in create_person and batch_create_persons, potentially causing confusion about when to use it separately.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_person, get_chat_messages, update_profile). The naming is predictable and clear, with no mixing of conventions.
11 tools is appropriate for a client management system with profile, chat, and compass features. The scope is well-defined and each tool serves a clear function without unnecessary bloat.
The tool set supports create, read, and search operations for people, but lacks update and delete functionality. Also, there is no explicit tool to update a client's compass after creation, and chat management is limited to send and retrieve without edit/delete.