glm_code_run

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

The description mentions 'sandbox' but does not elaborate on behavioral constraints (e.g., file access, network, error handling). With no annotations, the description fails to disclose what happens during execution or return format.

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 extremely concise (3 words) but lacks structure. It adequately conveys the basic purpose but omits critical details, making it too minimal for a code execution tool.

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?

Given the tool's complexity (code execution, no output schema, no annotations), the description is insufficient. It does not cover return values, error handling, or sandbox limitations, leaving significant gaps.

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 coverage is 100% with clear descriptions for both parameters. The description adds no extra meaning, but the schema already provides adequate semantics. Baseline 3 is appropriate.

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 'Python 코드 실행 (샌드박스)' clearly states the tool's purpose: executing Python code in a sandboxed environment. It distinguishes from siblings like glm_shell_exec (general shell execution).

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?

No usage guidelines provided. The description does not indicate when to use this tool over alternatives like glm_shell_exec or mention prerequisites or limitations.

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