getMyChatsDevuelve las conversaciones del usuario autenticado con cuidadores asignados a sus órdenes. Cada conversación incluye identificador, orden asociada, estado, fecha del último mensaje y una vista previa breve. Para acceder al contenido completo de los mensajes, utilizar getChatMessages.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It explains what each conversation includes (identifier, order, status, last message date, preview) and implicitly notes that full messages are excluded by directing to getChatMessages. It does not mention pagination or error conditions, but the key behavior is transparent.
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 the main purpose and return details. The second sentence adds a useful pointer to a sibling without unnecessary fluff. Every sentence earns its place.
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 simple list tool with no output schema or annotations, the description covers the essential return values and provides a navigation hint to getChatMessages. It could mention ordering or limits, but given the simplicity, it is largely complete.
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 tool has zero parameters, and the input schema is empty. According to the rubric, baseline 4 applies for 0 params. The description adds no parameter-specific information because none 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 uses a specific verb ('Devuelve') and clearly identifies the resource ('conversaciones del usuario autenticado con cuidadores asignados a sus órdenes'). It differentiates from siblings by specifying that each conversation includes summary fields and that full message content is handled by getChatMessages.
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 explicitly states when to use this tool versus an alternative: 'Para acceder al contenido completo de los mensajes, utilizar getChatMessages.' This provides clear guidance on what the tool returns and when to choose a sibling.
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 resource or action: coverage checks, lead capture, order creation, breed catalog, chats, orders, pets, service catalog, shifts, and messaging. No two tools could be confused for the same purpose.
All tool names follow a consistent camelCase verb_noun pattern (checkCoverage, createLead, createOrder, getBreeds, getChatMessages, etc.). The pattern is predictable and uniform across the entire set.
12 tools is well-scoped for a pet service booking assistant. Each tool covers a clear need without being excessive or sparse.
Core workflows are covered: coverage, ordering, pets, chat, and service catalog. Minor gaps exist like no update/cancel order or add/edit pet, but agents can work around these as the primary booking flow is complete.