madeonsol_price_alerts_create

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

Discloses key behavioral traits: captures baseline, fires on drop, fires again on recovery, and returns webhook_secret only once. Adds value beyond annotations, which already indicate mutation and non-idempotency.

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?

Four sentences, no fluff, front-loaded with core action. Every sentence provides important 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?

Explains alert logic and return value adequately. Could mention default delivery_mode or behavior when no price available, but overall complete for an agent to use correctly.

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%, so baseline is 3. The description adds meaning by explaining the firing logic (drop_pct and recovery_pct interaction with baseline) and notes the return of webhook_secret once, which is not in 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?

Clearly states the verb 'Create' and resource 'price alert'. Explains the mechanism (captures baseline MC, fires on drop, optional recovery) and distinguishes from other alert tools like coordination_alerts_create.

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 context for when to use: to set up price-based alerts with drop and optional recovery. Does not explicitly state alternatives or when not to use, but the tool name and sibling list make differentiation clear.

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