create_price_alert

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

Annotations are empty, so the description carries the full burden. It discloses the authentication requirement (IWMM_API_KEY) and the constraint that at least one threshold must be provided. However, it does not detail side effects (e.g., duplicate alerts), error behavior, or sync/async nature.

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 two sentences with no wasted words. It efficiently communicates the tool's purpose, parameter constraints, and a key prerequisite.

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 simple creation tool with no output schema, the description covers the core behavior. It could optionally mention the expected response (e.g., returns the created alert), but the current level is adequate.

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 100%, but the description adds critical business logic: 'Supply increasePct, decreasePct, or both (Premium). At least one threshold is required.' This clarifies the relationship between parameters and the premium feature, going beyond the schema's individual property descriptions.

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 'Create a price alert for a card' clearly identifies the action and resource. It further specifies that the alert can be set for increasePct, decreasePct, or both (Premium), distinguishing it from related sibling tools like delete_price_alert, update_price_alert, and list_price_alerts.

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 states 'At least one threshold is required' and 'Requires IWMM_API_KEY', providing clear prerequisites. It does not explicitly mention when not to use the tool, but the context is sufficient for the agent to decide.

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