zen_clear_browsing_data

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

No annotations are provided. The description discloses the destructive nature (clear) and lists the data types affected, which is sufficient. However, it does not detail any side effects, permissions needed, or confirmation requirements, which limits transparency for a destructive action.

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 extremely concise: two sentences for the main purpose, followed by clear parameter explanations. No unnecessary words, well-structured, and front-loaded with the action.

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?

Given the simple 2-parameter tool with no output schema, the description covers the essential context: what types are cleared, default behavior, and optional timestamp filter. It could benefit from mentioning that the operation is irreversible or that it returns nothing/an empty response, but overall it is mostly complete.

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 input schema has no descriptions (0% coverage), but the description fully explains both parameters: 'types' lists possible values and default behavior, 'since_ms' defines the timestamp meaning. This adds complete semantic meaning beyond the schema.

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 clearly states the tool clears browsing data of specified types, listing them explicitly. It distinguishes the action (clear) from sibling tools like zen_cache or zen_cookies, but does not explicitly differentiate when to use this tool versus those individual ones.

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 the usage context (which types to clear, optional timestamp filter) but offers no guidance on when to use this tool vs. alternative sibling tools like zen_cache or zen_downloads. It implies usage for bulk clearing but lacks explicit when-not or alternatives.

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