Create Price Alert

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

The description adds substantial behavioral context beyond annotations: persistent, writes to account, requires API key, notifies by email and optionally webhook, triggers on threshold crossing, persists until deleted. Annotations already indicate non-read-only, but description enriches with precise details. No contradiction.

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 concise (3-4 sentences), front-loaded with key information, and every sentence adds value. No unnecessary words or repetition.

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 5 parameters and no output schema, the description covers purpose, usage context, side effects (persistent, requires API key), and related tools (opa_list_price_alerts, opa_delete_price_alert). It is self-contained and answers common agent questions.

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 coverage is 100% with descriptions for each parameter, so the description does not need to add much. It provides a usage example and mentions webhook optionality, adding marginal value. Baseline 3 is appropriate.

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 it creates a persistent price alert, watches live prices, and notifies the user. It distinguishes from siblings by specifying creation vs. listing/deletion, and provides a usage example. The verb 'Create' and resource 'price alert' are explicit.

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 explicitly says when to use: 'when the user asks to be alerted/notified when a price goes above or below a level'. It mentions the requirement of an API key and writes to the account, but does not explicitly state when not to use or provide direct alternatives beyond listing/deletion.

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