reset_dataset_cache

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

No annotations provided, and the description only notes the permission requirement; it fails to disclose behavioral traits such as side effects, whether the action is destructive, or what happens to ongoing queries.

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?

Two concise sentences with front-loaded action and permission info; every clause adds value without redundancy.

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?

With an output schema present, the description is not required to detail return values, but it omits any context on what constitutes a successful reset or error conditions, making it minimally adequate.

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 has 0% description coverage and the tool's description does not explain 'dataset_id' beyond mentioning 'a specific CDV dataset', leaving the agent without guidance on format, example, or how to obtain the ID.

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?

Description clearly states the action (reset cache) and target (CDV dataset), distinguishing it from the sibling tool 'reset_dataconnection_cache' which resets data connection caches.

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?

Only mentions a permission requirement ('ds_manage'), with no guidance on when to use this tool versus alternatives, or conditions when not to use it.

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