set_market_alert

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

Annotations indicate non-read-only and non-destructive. Description adds that it subscribes to future notifications, mentions free vs Pro tiers, and explains delivery channel behavior. No contradictions.

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 slightly long but each sentence adds unique value. It front-loads purpose, then constraints, then examples, making it easy to parse. Minor redundancy in 'set_market_alert' example could be trimmed.

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?

Lacks details on response format, alert frequency, or how to unsubscribe. For a simple subscribe tool with no output schema, it covers essential usage but leaves some operational questions unanswered.

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%, but description adds context: market slugs from rank_markets, channel meanings, destination ignored for email, and a concrete example. This goes well beyond the schema 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 clearly states the verb 'Subscribe' and specific resource 'movement alerts for a DCPI market', distinguishing it from read tools like get_market_dcpi_rank. It also differentiates from sibling alert tools by focusing on market 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?

Explicitly tells when to use (monitor markets, not query), when not to use (for reading now), and provides prerequisites (bind_email for email, Pro for webhook). It also names the alternative get_market_dcpi_rank for reading.

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