cubism_clear_parameter_values

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

No annotations are provided, so the description must carry full burden. It mentions clearing cache and restoring state but does not disclose side effects, whether it is destructive, or prerequisites. For example, it doesn't say if it affects all parameters or requires certain permissions. This leaves significant gaps.

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 short and front-loaded with the primary action. The inclusion of an Args section adds structure, though it is not standard for MCP descriptions. Overall, it gets to the point with minimal fluff.

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?

While an output schema exists (not shown), the description does not explain the 'temporary parameter value cache' concept or what happens after clearing. It lacks details on behavior, error conditions, or behavioral impact. Given the tool's complexity (mutation related to parameter state), the description is insufficient for full understanding.

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%, meaning the description does not explain the parameter. The Args section lists 'model_uid' but provides no additional definition, type, or format beyond the schema. The description adds minimal value for parameter understanding.

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 action: clearing temporary parameter value cache sent to the model and restoring state. It uses a specific verb ('清除' - clear) and resource ('临时参数值缓存' - temporary parameter value cache). It also mentions pairing with SetParameterValues, which distinguishes its role among siblings, though not fully differentiating from all tools.

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 says it is used with SetParameterValues, providing context for when to use it. However, it does not explicitly state when not to use it or mention alternatives like cubism_get_parameter_values or cubism_edit. The guidance is implied but lacks exclusions.

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