execute_tool

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, permissions, error handling, or limitations of the proxy execution. The description is too brief to inform the agent about important runtime behaviors.

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 a single succinct sentence that front-loads the core purpose. However, it could be slightly more structured (e.g., mentioning output or usage order). The Korean language may pose a barrier for non-Korean agents, but the content is efficiently concise.

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 lack of output schema and annotations, the description should provide more context about return values, error conditions, or prerequisites. It only states the mechanism (proxy execution) without informing the agent about what happens after execution or any constraints, making it incomplete for a meta-tool.

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 100%, so baseline is 3. The description adds minimal value beyond the schema ('tool_name + params'). It does not provide additional meaning or examples for the parameters, but the schema already documents them adequately.

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 it is a proxy execution tool for tools from discover_tools, with specific verb '프록시 실행' (proxy execute). It distinguishes from sibling tools that are specific domain tools, making it clear that this is a dynamic dispatcher.

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 implies usage after discover_tools by mentioning 'discover_tools 결과 도구를 프록시 실행' (proxy execution of tools from discover_tools results). However, it does not explicitly state when not to use it or provide alternative guidance, leaving some ambiguity for agents unfamiliar with the context.

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