get_manufacturing_order

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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing beyond the word 'Get'. It doesn't disclose what happens when the ID is unknown, whether the read is safe/cached, or what the returned payload contains. A read-only implication is inferable from the verb but is never confirmed.

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?

A single short sentence with no filler and the essential resource front-loaded. It is efficient, though its brevity edges toward under-specification rather than genuine conciseness.

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 lookup tool with no output schema, no annotations, and an undocumented 'include' parameter, the description is too thin. An agent lacks the return-shape and parameter-expansion context needed to call it confidently.

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 only 50%: manufacturingOrderId is documented in the schema, but the 'include' array has no description anywhere. The description neither explains what 'include' expands nor how the order ID is formatted, so it fails to compensate for the coverage gap.

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 clear verb ('Get') and resource ('manufacturing order') with a scope qualifier ('a specific'). An agent can tell it fetches one order by ID, but the description does nothing to separate it from near-neighbors like list_manufacturing_orders or get_manufacturing_order_trace.

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?

There is no when-to-use guidance at all. With siblings such as list_manufacturing_orders, get_manufacturing_order_trace, upsert_manufacturing_order, and set_manufacturing_order in the toolset, the description gives no cue about when this fetch is the right choice or what prerequisites it needs.

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