stata_export_graph

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?

在缺少注释和输出模式的情况下，描述提供了基本功能但未覆盖关键行为细节（如默认文件名、覆盖、错误处理）。对于只有4个可选参数的工具来说不算严重缺陷，但可以让调用者更好地准备依赖默认行为。

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?

输入模式覆盖率为100%，所有参数在模式中都有描述，包括枚举、默认值和说明。描述本身没有添加额外的参数语义，因此根据基线规则打3分。

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?

描述明确说明了动作（导出）、资源（内存中的图）和结果（图片文件，返回路径和大小）。这使它有别于运行或获取结果的兄弟工具。唯一小的不足是“图”没有进一步说明，但总体上足够清晰。

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?

描述未提供任何何时使用、何时不用或替代方案的指导。没有提及前置条件（如必须存在图）或与兄弟工具的比较，只能依赖工具名称和语义推断用途。

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