gold_get_order

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

With no annotations provided, the description carries the behavioral burden. It discloses the HTTP method (GET, implying read-only) and meaningful auth behavior ('BYOK fail-closed'). It does not describe return values or error behavior, but these are less critical for a simple retrieval tool.

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 very compact and front-loads the core API call. However, 'Gold PRO $29' is marketing noise that does not help an agent select or invoke the tool correctly.

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 one-parameter GET tool, the description is mostly sufficient, but it leaves out expected return shape, success/error scenarios, and any clarification of 'BYOK' or 'Gold PRO'. These gaps are noticeable because there is no output schema or annotation to fill them.

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 schema has one undocumented numeric id parameter (0% coverage), but the endpoint template 'orders/{id}' establishes that id is the Woo order ID. This partially compensates for the lack of schema descriptions, though an explicit statement would be stronger.

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 ('get'), a specific resource ('Woo order'), and the exact endpoint ('GET /wp-json/wc/v3/orders/{id}'). This makes it easy to distinguish from siblings like gold_list_orders and gold_get_product.

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 required id parameter and singular 'get' imply this is for retrieving one order by ID, but the description never explicitly says when to use it versus gold_list_orders or gold_get_product. Usage context is left to inference.

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