create_price_alert

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

Discloses that it creates a resource (mutation) and requires an API key. Without annotations, it partially covers behavior but omits details like idempotency, side effects, or error scenarios.

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?

Three concise sentences with no fluff. Front-loaded with purpose, threshold requirements, and auth. Every sentence adds value.

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?

Covers main points but misses expected output (e.g., returns created alert ID). No output schema provided, so description should hint at return. Adequate for simple tool but not fully complete.

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%, but description adds critical info: at least one of increasePct or decreasePct is required (beyond schema which only requires cardId). This clarifies usage beyond schema alone.

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?

Clearly states creating a price alert for a card. Specifies the action (create) and resource (price alert). Differentiates from siblings like update_price_alert and delete_price_alert.

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 guidance on when to use: requires supply of increasePct, decreasePct, or both, and at least one threshold is mandatory. Mentions API key requirement. Lacks explicit exclusions or alternatives but sufficient for basic usage.

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