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

The description adds no behavioral context beyond the annotations. It does not disclose expected return behavior, data scope, or any operational constraints. The annotations already declare it safe and read-only, but the description contributes nothing additional.

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?

At two words, it is extremely concise but under-specified. Conciseness should not come at the cost of clarity; the phrase 'Single product.' does not earn its place because it conveys almost no useful information.

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?

Although the output schema exists and annotations provide safety context, the description does not state the tool's primary function or identify the resource being acted upon. A 1-parameter tool can be adequately documented with a clear verb and resource, but 'Single product.' leaves the operation ambiguous.

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%, and the description does not explain the product_id parameter. No format, meaning, or examples are given in the description, leaving the agent to guess that 'BTC-USD' might be a currency pair. The description fails to compensate for the schema's lack of parameter details.

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 'Single product.' is a noun phrase with no verb or action, so it does not clearly state what the tool does. It hints at a singular resource versus the plural sibling 'products', but fails to specify whether it retrieves, creates, or modifies a 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?

No guidance is given on when to use this tool versus alternatives like product_ticker or product_stats. There is no mention of use cases, prerequisites, or exclusions.

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