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

With no annotations provided, the description carries the disclosure burden. It does disclose a meaningful behavioral constraint: results come from saved checks, not live or fresh data. However, it does not clarify side effects, read-only enforcement, error cases, or how the optional period parameter affects behavior.

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 two short, focused clauses with no filler. Every sentence adds useful information: one defines the purpose and data source, the other defines the item input format.

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 description is adequate for a basic invocation: the required item parameter is explained and the overall behavior is clear. It is not fully complete because the days parameter is undocumented, and there are no annotations to clarify safety or data-source limitations, though the presence of an output schema reduces the need to describe return values.

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 provides no descriptions, and the description adds meaning for the required item parameter by stating it can be a link or article. However, it says nothing about the optional days parameter, its default, or how it controls the reported period, leaving a notable semantic gap.

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 clearly states that the tool reports how a product's price changed over a period based on saved checks, and it specifies that the product is identified by link or article. This is enough to distinguish it from siblings like parsee_get_prices or parsee_monitor_changes, though it does not explicitly name any alternative.

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 the tool is for retrieving historical price trends of a specific item from previously saved checks. It does not explicitly state when to prefer this tool over alternatives such as parsee_get_prices, nor does it describe exclusions or prerequisites beyond the implied reliance on saved checks.

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