getMyOrdersDevuelve un resumen de las órdenes activas e históricas del usuario autenticado (paseos, adiestramiento, guardería, internación) con su estado actual. Para obtener el detalle completo de una orden, utilizar getMyOrderDetail.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the tool returns a summary (not full detail), includes both active and historical orders, and includes current status. This is useful behavioral context beyond the name/title. However, it doesn't explicitly state read-only behavior or response format, but the name and zero params make mutation unlikely.
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 only, with the purpose front-loaded and the alternative tool mentioned in the second sentence. Every word earns its place, keeping it concise and easy to parse.
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 parameters, output schema, or annotations, the description provides sufficient context: it names the resource, includes the scope (active/historical), lists order types, and mentions current status. It also points to the detail tool for more complete information. Slight gap is that it doesn't specify the response structure, but the word 'resumen' implies a condensed representation.
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?
With zero parameters, the baseline is 4 per the rubric. The description does not need to explain parameters since none exist. The schema coverage is trivially 100%, and no additional parameter context is required.
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 un resumen' (returns a summary) with a clear resource: the authenticated user's orders. It lists the order types (paseos, adiestramiento, guardería, internación) and explicitly differentiates from the sibling tool getMyOrderDetail by pointing to it for full detail.
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?
Provides explicit usage guidance: use this tool for summaries of active/historical orders, and use getMyOrderDetail for complete order detail. This clearly distinguishes when to use this tool versus an alternative.
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.