distru_get_productFetch a product by its UUID to retrieve its full details. Use this when you have the exact product ID and need the record.
Fetch one product by id (GET /public/v1/products/{id}). Returns 404 if the id does not exist on this account. Ids are opaque UUID strings - never construct or parse one.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The product UUID. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint and openWorldHint annotations, the description discloses important behavior: a 404 is returned when the id does not exist on this account, and ids are opaque UUIDs that must never be constructed or parsed. This gives the agent practical guidance for handling failures and id values.
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 three short sentences, front-loaded with the primary action and endpoint. Every sentence adds distinct value: what it does, failure behavior, and id-handling guidance. No wasted 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?
For a simple single-parameter read operation, the description covers the action, endpoint, error case, and id semantics. The annotations cover safety, and no output schema is needed because the operation is straightforwardly 'fetch one product'.
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 input schema already documents the id parameter well, and schema coverage is 100%. The description adds valuable extra meaning by warning that ids are opaque and must never be constructed or parsed, which goes beyond the schema's 'The product UUID.'
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 verb and resource: 'Fetch one product by id' with the exact endpoint 'GET /public/v1/products/{id}'. It clearly distinguishes this from sibling tools like distru_list_products by focusing on single-record retrieval by id.
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 clearly implies when to use this tool: when you need one product by id. It does not explicitly name alternatives or say 'use list_products to browse', but the single-id scope and endpoint make the usage context unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.