alert_delete

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

With no annotations, the description carries the full burden and does disclose that this is STATE_MUTATING and deletes from the user account. It also documents the delete_all limitation. It stops short of stating permanence, required scopes, or failure behavior, so it is good but not exhaustive.

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?

Three short labeled sections (WHEN TO USE, SIDE EFFECTS, LIMITATIONS) front-load the essential information with no wasted wording. The structure makes it easy for an agent to scan the key constraints.

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 a one-parameter delete tool with no output schema and no annotations, the description covers purpose, usage, side effects, and the delete_all option. It omits return/error behavior, but the core decision and invocation inputs are well covered.

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% and the single parameter is already documented in the schema. The description's 'Pass delete_all: true to clear all alerts' largely repeats that, adding only minor usage framing, so the baseline of 3 is appropriate.

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?

States a specific verb (Delete) and resource (active alerts from TradingView alerts list), and the action is clearly distinct from sibling tools alert_create and alert_list. An agent can tell this removes alerts rather than displaying or creating them.

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 WHEN TO USE section gives clear triggering conditions: removing triggered, obsolete, or batch alerts. It does not explicitly name alternatives or when not to use it, but the context is sufficiently clear for correct invocation.

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