os_downloads_get_product

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds only that it retrieves 'metadata', implying a non-destructive, lightweight operation, but it does not add context about authentication, rate limits, or any side effects. With annotations present, this is adequate but not enriched.

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 concise sentence with no filler. It is front-loaded with the core action. However, it could arguably include a bit more context without becoming verbose, but as written it is appropriately brief.

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?

The tool is simple (one required parameter, no nested objects) and an output schema exists, so return values need not be described. However, the description lacks usage guidance and does not mention prerequisites (e.g., the product must exist or how to discover product IDs). It is minimally sufficient but not complete.

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 0%, so the schema provides no explanation for productId. The description merely repeats 'by productId' without clarifying what a productId is, where to obtain it, or its format. Since the description must compensate for the missing schema documentation but does so minimally, this scores low.

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 ('Get'), a specific resource ('OS Downloads product metadata'), and the identifier ('productId'). This clearly distinguishes it from sibling tools like os_downloads_list_products (which lists products) and os_downloads_get_export (which retrieves an export). The purpose is unambiguous.

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 guidance on when to use this tool versus alternatives. Sibling tools include list_products and get_export, and the description does not explain how this tool fits into a workflow (e.g., 'use after os_downloads_list_products to get details for a specific product'). No exclusions or conditions are mentioned.

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