gold_get_product

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds valuable detail through the HTTP method GET, the 'BYOK' authentication requirement, and the 'fail-closed' behavior, which tells the agent that the tool will error rather than proceed without a valid key.

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 concise and front-loads the key operational details: endpoint, plan requirement, and auth behavior. The 'Gold PRO $29' token is slightly extraneous but relevant as a prerequisite.

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 one-parameter read operation, the description is fairly complete: it names the endpoint, the auth expectation, and failure behavior. However, with no output schema and no annotations, it does not describe the return value shape or error cases, which the agent might need to validate the tool's result.

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%, and the description does not add meaning beyond the schema's 'product id' parameter. The endpoint path confirms id is a path parameter, but this is already implied by the tool's purpose and 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?

The description states a specific action ('get single Woo product') and the exact REST endpoint, which clearly distinguishes it from sibling tools like gold_list_products or gold_create_product. Including the path /wp-json/wc/v3/products/{id} leaves no ambiguity about the resource being retrieved.

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 description implies it is for retrieving one product by ID, and the 'Gold PRO $29' phrase indicates a license prerequisite. However, it does not explicitly state when to prefer this over gold_list_products or mention any alternatives or exclusions.

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