Cleans up browser profile cache

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is partly covered. The description adds the workspace scoping of the cleanup but does not say which cached artifacts are removed, whether the profile itself is preserved, or whether the operation is repeatable. Note: removing cached data arguably conflicts with destructiveHint=false, but cache regeneration is a defensible exemption, so this is borderline rather than a clear contradiction.

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 that front-loads the action and target. It is slightly padded by the "This method can be used to" construction, which could be trimmed without loss.

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?

There is no output schema, so the description should ideally indicate what the caller gets back or what state the profile is left in. It covers the scope but leaves the effect of the cleanup, and the identity of the "cached data," unspecified for a mutating tool.

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 100%, so both profileId and workspaceId (including the -1 default) are fully documented in the schema. The description's reference to "the specified workspace" merely paraphrases the schema, so the baseline 3 applies.

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 clear verb and resource: cleaning cached data for a browser profile, scoped to a workspace. It is distinguishable from delete_profile or update_profile at a glance, though it does not explicitly name or contrast with any sibling tool.

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?

"This method can be used to..." gives no when-to-use guidance, no prerequisites, and no mention of alternatives such as delete_profile or recover_profile. The only usage signal is implicit in the word "clean up".

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