get_product

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

With no annotations, the description carries the full burden. It discloses that prices are in RUBLES and that it fetches a single product, which implies a read operation. But it does not mention authorization, error behavior, or the effect of the `raw` parameter beyond the schema, leaving the behavioral profile somewhat thin.

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 a single, front-loaded sentence that states the core action ('Get a single product by UUID') and a key output detail ('Prices returned in RUBLES'). Every word serves a purpose; no redundancy or filler.

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 get-by-id tool with two well-documented parameters and no output schema, the description is largely complete. It could be improved by noting the alternative search_products for cases where the UUID is unknown, but the current information is sufficient for straightforward use.

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 fully describes both parameters: `id` as a Product UUID and `raw` as a boolean for returning the raw MoySklad object. The description adds no additional parameter semantics, so the baseline of 3 for high schema coverage applies.

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 'Get a single product by UUID' is a specific verb+resource+method that precisely defines the tool's function. It also adds 'Prices returned in RUBLES', a distinctive detail that differentiates it from other retrieval tools like search_products or get_stock.

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?

Usage is implied by 'by UUID'—the tool is for when you have a product UUID. However, it does not explicitly state when NOT to use it or mention alternatives like search_products for finding products without a known UUID. Thus, guidance is present but implicit.

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