creo_get_dimensions

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

注解已经声明了 readOnlyHint=true、idempotentHint=true、destructiveHint=false，描述也重申了“只读”，两者一致。描述额外补充了返回的尺寸属性字段，但没有解释失败模式、权限要求或关系驱动状态带来的行为影响；在已有注解覆盖安全画像的情况下，描述的价值有限。

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?

对于只有一个可选参数、无输出 schema 的只读工具，描述已经说明了工具用途、支持的目标模型来源以及返回的字段类别，足以支持调用决策。唯一欠缺的是未描述返回的具体格式或可能的失败情况，但对这个复杂度的工具而言并非关键缺口。

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?

input schema 对唯一参数 model_file 的说明已经是“可选；安全输出目录中的零件文件名。省略时读取当前模型。”，schema 覆盖率为 100%。描述中的“当前 Creo 零件或安全输出目录中某个零件副本”基本只是复述 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?

描述以“只读列出”这一具体动词确立了操作，并明确资源是 Creo 零件或安全输出目录中的零件副本，还列出了返回的内容（尺寸 ID、符号、数值、类型、关系驱动状态、所属特征）。这一描述足以与 creo_get_project_dimensions 等兄弟工具区分开，因为限定了安全输出目录副本和当前模型两种来源。

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?

描述给出了使用场景的部分上下文：省略 model_file 时读取当前模型，指定 model_file 时读取安全输出目录中的副本。但未明确说明何时应使用本工具而非 creo_get_project_dimensions 或 creo_get_features 等替代工具，也没有排除性说明。

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