ytptube_clear_history

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

Annotations already state destructiveHint=true, but the description adds valuable context by clarifying that media deletion is opt-in and that records can be selected by IDs or a status filter. This goes beyond the annotations by explaining what can be destroyed.

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, well-structured sentence with a front-loaded verb ('Delete') and no redundant information. Every word contributes to understanding the tool's 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 description covers core selection methods and media deletion behavior, but it omits that 'type' is required, the possibility of bulk deletion when using a status filter, and the irreversibility of the delete action. Given this is a destructive tool with no output schema, more warnings and parameter context would improve completeness.

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. It mentions IDs, status filter, and opt-in media deletion, but it does not explain the required 'type' enum (queue vs done) or the format/available values for 'status'. The description adds some meaning but leaves key parameter semantics unclear.

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 'Delete' and identifies the resource as 'queue/history records', with clear selection criteria (IDs or status filter). This distinguishes it from siblings like ytptube_list_history and ytptube_retry_history_item.

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 clearly implies when to use this tool: when you need to remove queue/history records by IDs or status. It does not explicitly name alternatives or exclusions, but the context is sufficiently clear for a deletion tool.

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