clear_all

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

No annotations are provided, so the description carries the full burden. 'Delete' indicates destructive behavior, but there is no statement about permanence, irreversibility, or side effects. The description adds little beyond the tool's purpose and does not disclose behavioral traits such as whether deletion is permanent or how multiple filters combine.

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?

A single sentence with no filler; the core action and optional scoping are front-loaded. Every word earns its place.

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 tool with two optional params and no output schema, the description is short but mostly adequate. It does not clarify param combination semantics or warn about irreversible bulk deletion, which are relevant for an agent invoking a destructive operation. Overall, it is minimally viable.

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?

The schema has no descriptions (0% coverage), so the description must compensate. It does map the parameters to 'of a test_id/app', which gives them some meaning as filters. However, it fails to explain how the two parameters interact (e.g., AND or OR) or that omitting both deletes everything.

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 a clear resource 'all captured messages', with an explicit optional scope by test_id/app. This distinguishes it from siblings like clear_channel or delete_app, which target different resources.

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 the tool is used when you want to delete captured messages, optionally filtered by test_id or app. It does not explicitly mention alternatives, conditions, or when not to use it, leaving the agent to infer the scope from the sibling list.

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