set_market_alert

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

Annotations already indicate the tool is not read-only and not destructive, but description adds context: it subscribes to future events, not immediate reads. It explains tier differences (free email, Pro webhook). Could mention more about duration or limits, but overall good.

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?

Description is well-structured with multiple informative sentences, no wasted words. Slightly lengthy but each sentence adds value. Could be slightly more concise, but still effective.

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 no output schema and 3 parameters, description covers purpose, prerequisites, tier differences, and example. However, fails to describe return value or confirmation after subscribing, and does not mention how to unsubscribe. Missing some completeness for a subscription tool.

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 has 0% description coverage, so description must compensate. It explains channel values and destination format, and provides a concrete example for market. However, market parameter lacks definition or valid values beyond the example, leaving some ambiguity.

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?

Description clearly states the tool subscribes to movement alerts for a DCPI market, using specific verbs like 'subscribe' and 'get notified'. It explicitly distinguishes from the sibling tool get_market_dcpi_rank, which reads current data.

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 explicit when-to-use and when-not-to-use guidance: call bind_email first for email, mentions free vs Pro tiers, gives an example, and cautions not to use for reading (use get_market_dcpi_rank instead).

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