clear_annotations

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It clearly states the destructive action ('deletes all') and the output (deleted count), which is important safety information. However, it doesn't mention irreversibility or any additional side effects, so it's not a 5.

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 a single sentence that efficiently conveys the action, scope, and return value. There is no wasted information, and it is front-loaded with the core function.

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?

The tool is simple, and the description covers the essential behavior and return count. It lacks explicit handling of edge cases (e.g., no annotations) and the optional parameters' purpose, but the description is largely self-contained given the tool's simplicity.

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 description coverage is 0%, so the description must compensate for parameter meaning. It clarifies that symbol and timeframe define the scope of deletion, but it doesn't explain the purpose of request_id or idempotency_key. The description adds some value over the raw schema but leaves the optional parameters undefined.

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 uses the specific verb 'siler' (deletes) and clearly identifies the resource: annotations for a given symbol and timeframe. It also states the return value (deleted count), distinguishing it from siblings like get_chart_annotations and annotate_chart.

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 implies this tool is for clearing all annotations for a symbol/timeframe, but gives no explicit guidance on when to use it over alternatives or any exclusions. It doesn't mention that it should be used before re-annotating or that it is the inverse of adding annotations.

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