tickerbot_subscribe_ticker

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

With no annotations, the description carries the transparency burden. It discloses the core behavior: the webhook fires when the condition matches, and it explains how POST/Discord/in-app delivery works. It does not cover webhook lifecycle (e.g., persistence, cancellation, failure handling) or mention cadence, but the schema covers cadence. The description adds useful context on channel selection.

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 two sentences: purpose first, then usage details. It is front-loaded, uses concrete examples, and avoids unnecessary words. Every sentence adds value.

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?

For an 8-parameter subscription tool with no output schema and no annotations, the description covers the core use case well: condition, channel selection, and delivery destination. It omits some details (mobile_push, device_id, cadence) but those are all described in the schema. The description provides enough context for an agent to select and call the 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 coverage is 100%, providing baseline 3. The description adds value beyond schema by giving a concrete SQL condition example and explaining how to configure delivery channel (target_url for HTTPS POST, discord_url for Discord, omit for in-app). It does not cover all parameters, but the schema descriptions are sufficient.

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 states a specific action: 'Register a webhook that fires when one ticker matches a condition.' It clearly scopes to a single ticker and a condition-based trigger, differentiating it from sibling subscription tools like subscribe_signal or subscribe_events.

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 on when to use the tool: for ticker-specific condition alerts. It explains the condition syntax, delivery channel options, and how to choose between webhook, Discord, or in-app. It does not explicitly name alternative tools or exclusions, but the scoping language ('one ticker', 'scoped to that ticker') implies it's for per-ticker conditions.

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