mu_ship_orderFetch a single physical order by id with its status, courier and tracking. Address/phone are masked unless reveal=true. Owner-only.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | catalog_orders.id of the order. | |
| reveal | No | Show full address/phone (default false = masked). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description covers key behaviors: address/phone masking controlled by reveal parameter, and ownership restriction. Missing details on error handling or idempotency, but main traits are disclosed.
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 concise sentences that front-load the purpose and immediately add critical behavioral context. No unnecessary words.
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 simplicity of the tool (2 params, no output schema), the description covers all essential aspects: what is returned, masking behavior, access control. Could mention error handling, but not required for basic usage.
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% with good descriptions. The description adds minimal extra meaning beyond 'by id' and 'masked unless reveal', essentially reinforcing 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?
Clearly states it fetches a single physical order by ID, with specific fields (status, courier, tracking). This distinguishes it from list tools like mu_ship_orders.
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?
Specifies 'Owner-only' as a prerequisite but does not explicitly describe when to use versus alternatives. However, the name and context make it clear for single order retrieval.
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 has a clearly distinct purpose; no two tools appear to do the same thing. Even closely related tools (e.g., mu_quote vs mu_rfq_create, mu_preview_mockup vs mu_create_product) are differentiated by read-only vs. action, or draft vs. send.
Tool names consistently use snake_case with the mu_ prefix, and follow a clear verb_noun or noun_verb pattern. Groups like mu_gi_*, mu_ship_*, mu_rfq_* maintain internal consistency. No arbitrary or ambiguous names.
The tool count of 28 is on the higher side but appropriate for the breadth of functionality (registration, product lifecycle, manufacturing, shipping, sales, admin). It's well within a manageable range for a comprehensive server.
The tool surface covers core workflows comprehensively: registration, product CRUD (with create, update, retire), manufacturing quotes (informational and RFQ with spec drafting), shipping (CSV, tracking, status updates), sales data, and gi-specific management. Minor gaps include lack of store update/delete and product search, but these are not critical for the main use cases.