Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the readOnly/openWorld annotations: it discloses the data-hygiene behavior (card numbers, coupons, credential-bearing document/media links stripped), that status codes are spelled out, that workflow and PO data are opt-in, and that supplier catalog tools are unavailable. Missing is behavior on an unknown invoice number (empty result vs error) and any auth/rate-limit note, which would complete the picture.

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?

Front-loads the core promise ('One order by invoice number with everything the API holds') and then enumerates payload contents in a compact run-on list. The trailing '(invoice number condition)' and the catalog-tools caveat are slightly out of place but each carries information; nothing is padding.

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?

With no output schema, the description carries the return-value burden and does so thoroughly by enumerating the order payload sections and noting redactions and status-code formatting. Combined with the endpoint reference and the optional-depth flags, an agent has enough to call it correctly and anticipate what comes back.

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 description coverage is 100%, so all four parameters are already documented, including that include_po_data implies workflow data. The description only restates that workflow items and PO data are 'optional', adding no syntax, format, or default nuance beyond the schema. Baseline 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?

States a specific verb and resource ('One order by invoice number') and immediately scopes it: 'everything the API holds', enumerating line items, payments, refunds, shipments, notes, taxes, store. This clearly separates it from siblings like deconetwork_search_orders and deconetwork_list_orders_due, which return sets rather than one fully-hydrated order.

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?

Implicitly positions itself as the single-order detail fetch versus the search/list siblings by emphasizing 'all line items ... everything the API holds', and flags the optional workflow/PO depth via the include flags. It also states a useful constraint ('Supplier catalog tools are unavailable') and pins the underlying call (GET /api/json/manage_orders/find), but never explicitly says when NOT to use it (e.g., when you only have a customer name, use search_orders).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.