apply_egovframe_recipe

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

No annotations provided, so description carries full burden. Mentions sequential execution and dryRun behavior. Does not disclose potential side effects like file overwriting, permissions required, or whether it modifies existing projects. Some behavioral context but missing important details.

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?

Two concise sentences with front-loaded main action. No redundant words. Every sentence provides essential information: what the tool does and how to preview the plan.

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?

No output schema, so description need not explain return values. However, it does not describe what happens after execution (e.g., output files, logs, success/failure indication). Missing prerequisites or dependency info. Adequate but could be more complete.

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 descriptions for all 6 parameters. The tool description adds no additional meaning beyond what the schema already provides. dryRun behavior is mentioned in both, so description adds minimal value.

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?

Description clearly states it selects a recipe, generates a project, and assembles common components (with optional AI components) sequentially. The verb '실행합니다' and resource '레시피' are specific. Distinguishes from siblings like create_egovframe_project (project creation alone) and add_egovframe_components (component addition separately).

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?

Describes dryRun=true for previewing the plan. Implies this tool combines project creation and component assembly, but does not explicitly state when to use vs. alternatives like creating a project first then adding components. Provides clear usage context but lacks exclusions.

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