cubism_get_parameter_values

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

无注解，描述承担全责。说明是只读操作、无需事务，未暗示任何副作用，行为透明充分。

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?

描述简洁，分为功能说明和参数解释两个段落，无冗余信息，每句都有作用。

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?

在有输出模式的情况下，描述不需要说明返回值。涵盖了参数用法和轻量级特性，对于获取参数值的简单工具而言足够完整。

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?

模式描述覆盖率为0%，描述对每个参数提供了含义：model_uid通过cubism_get_model_uid获取，ids可选且解释省略时的行为，增加了模式未提供的价值。

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?

描述明确使用动词'获取'和资源'参数值'，清晰表达功能。与兄弟工具cubism_set_parameter_values和cubism_clear_parameter_values区分开，指明不指定ids则返回全部参数。

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?

明确说明是轻量级读取操作，无需EditBegin/EditEnd事务，提供了使用上下文。虽未明确排除替代方案，但已足够指导何时使用。

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