opa_delete_price_alert

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

Discloses that deletion is permanent and requires an API key. With no annotations, this information is critical for safe usage. No contradictions.

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?

Very concise with only 4 sentences, each adding necessary information. Front-loaded with the core action.

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?

Given the tool's simplicity (one param, no output schema, no annotations), the description covers purpose, usage, prerequisite, and behavioral note (permanence, auth). No gaps.

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 schema already describes the id as a UUID. The description adds value by instructing to obtain the id via opa_list_price_alerts, which helps the agent use the parameter correctly.

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?

Description clearly states the action (delete) and resource (price alert) with specificity. It distinguishes from sibling tools like opa_create_price_alert and opa_delete_subscription by focusing on alert deletion.

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?

Provides clear when-to-use context ('remove/cancel/stop an existing alert') and prerequisite (get id from opa_list_price_alerts). No explicit when-not-to-use guidance, but the context is sufficient.

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