Watch a price

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

With all annotations being false, the description carries the burden and discloses key side effects: it starts tracking, stores a first observation, supports an optional target, and is subject to a free limit of 3 watches. This gives the agent a good understanding of the state changes and quota implications.

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 sentences, each earning its place: the first explains why to use it, the second states the core behavior, and the third gives a critical quota detail. It is front-loaded with the primary use case and contains no fluff.

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 tool with 4 parameters, no output schema, and minimal annotations, the description provides enough context to call it correctly: it explains the URL input, the initial observation, optional target, and the watch_refresh relationship. It does not cover failure modes or response format, but these are not strongly required given the absence of an output schema.

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 has 100% coverage, so the baseline is 3. The description adds minimal parameter context by mentioning 'optional target' and referencing re-reading via watch_refresh, but it does not deeply explain the semantics of url, label, currency, or target_price beyond what the schema provides.

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 tracks a product URL by storing the first price observation, and contrasts itself with a generic web tool that returns raw HTML without the price. It does not explicitly name siblings like price_add_manual, so it is clear but not fully differentiated from related tools.

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?

It gives a clear when-to-use directive ('Call this tool for any product URL') and explains why it should be used instead of a generic web fetch because that returns raw HTML without the price. It also mentions that re-reading is done via watch_refresh, providing a workflow, but does not mention conditions where alternatives like price_add_manual should be used.

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