getMyOrderDetailDevuelve información completa de una orden del usuario autenticado, incluyendo sesiones programadas, cuidador asignado y estado de pagos. Solo permite consultar órdenes pertenecientes al usuario autenticado.
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes | Identificador numérico de la orden, obtenido previamente desde getMyOrders. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the return content (sessions, caregiver, payment status) and the access constraint (only own orders), adding useful behavioral context. It does not mention error cases, but the read-only nature is implied by 'Devuelve'.
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, with the primary purpose front-loaded and a clear constraint in the second sentence. No redundant information, and 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?
For a simple get-by-ID tool with one parameter, the description is complete. It enumerates the key data returned and the authorization scope. The lack of output schema is not an issue because the description lists the included fields.
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 input schema covers 100% of the parameter, including a description stating that order_id is obtained from getMyOrders. The tool description adds no additional parameter semantics beyond the already implied ownership of the order, so the baseline of 3 is appropriate.
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 states a specific verb (Devuelve/returns), resource (order), and scope (authenticated user's own orders). It distinguishes from sibling tools like getMyOrders by emphasizing 'detalle completo' (complete detail) and the restriction 'Solo permite consultar órdenes pertenecientes al usuario autenticado'.
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 implies usage for retrieving full order details, but it does not explicitly compare with alternatives such as getMyOrders or createOrder. The schema parameter description references getMyOrders as the source for order_id, but the main description lacks a direct when-to-use guidance.
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.