list_price_alerts

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

No annotations are provided, so the description carries full burden. It discloses free tier limits and authentication requirement (IWMM_API_KEY). However, it does not mention response format, error handling, or potential default behaviors. Adequate for a simple read-only tool but missing some behavioral context.

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?

Two sentences, front-loaded with purpose. Every sentence provides essential information: purpose, limits, auth. No redundancy or wasted words.

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 (no params, no output schema, no annotations), the description covers purpose, usage limits, and auth. However, it lacks any mention of the output structure (e.g., list of alerts with fields), which would be helpful for complete understanding. Still, it's fairly complete for its complexity.

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 tool has no parameters (0 params, schema coverage 100%). Baseline for 0 params is 4. The description adds meaning beyond the schema by explaining the tool's purpose and usage limits. No further parameter details needed.

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 'List the authenticated user's price alerts,' using a specific verb ('List') and resource ('price alerts'). It distinguishes from sibling tools like list_buy_list or list_decks by naming the specific resource.

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 provides context about free tier limits and authentication requirement, but does not explicitly guide when to use this tool vs alternatives (e.g., create_price_alert, delete_price_alert). No when-not-to-use or alternative recommendations.

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