marketplace_watch

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that watches are re-run to report new listings, price drops, and target-price hits, but omits authentication needs, persistence behavior, what remove actually deletes, and what list returns.

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?

A single sentence that front-loads the actions and then defines the resource. It is dense but contains no filler, though it prioritizes purpose over operational detail.

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 10-parameter tool with no annotations, no output schema, and very low schema description coverage, the description is insufficient. It gives the purpose and the check_watches relationship but not enough detail for an agent to invoke add, list, and remove correctly across all parameters.

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 only 10%, and the description does not explain the action enum, name, queries, exclude, must_include, conditions, or price-bound parameters. It only loosely references a target price concept, leaving most of the 10 parameters semantically undocumented.

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?

States a specific set of verbs (save, list, remove) and a clear resource (a watch), then defines what a watch is. It explicitly connects to the sibling tool marketplace_check_watches, so an agent can distinguish managing watches from running checks.

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?

Implies usage by saying a watch is a saved comparison that marketplace_check_watches re-runs. However, it does not state when to add vs list vs remove, prerequisites for each action, or when not to use this tool versus other marketplace siblings.

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