list_price_alerts

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

With no annotations provided, the description carries the full burden of disclosure. It reveals that the tool lists only the authenticated user's alerts, explains tier constraints, and requires an API key. It does not explicitly state that it is a read-only operation, but 'list' implies idempotence.

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 a mere two sentences: the first states the core purpose, and the second adds constraints and auth requirements. It is front-loaded and contains no extraneous information.

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?

While the description covers purpose, constraints, and auth, it lacks information about the return format or the properties of each price alert. Since there is no output schema, the description should ideally enumerate response fields to fully inform the agent.

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?

There are no parameters, so schema coverage is 100%. The description adds value by explaining the authentication requirement and tier limits, which are not evident from the empty schema.

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 the tool lists the authenticated user's price alerts, using a specific verb ('list') and resource ('price alerts'). It differentiates from sibling tools like create_price_alert, delete_price_alert, and update_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?

The description provides context for when to use the tool by mentioning free vs premium tier limits and the requirement for IWMM_API_KEY. It does not explicitly state when not to use it or name alternatives, but the tier info helps guide usage.

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