create_egovframe_project

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

No annotations provided; description notes dryRun for preview but lacks details on potential destructive behavior (e.g., overwriting existing directories), required permissions, or error handling.

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, front-loaded with purpose, no unnecessary words.

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?

Briefly covers purpose and a key flag (dryRun) but omits output/return value description (no output schema). Given 7 parameters, schema already details them; additional behavioral or success criteria would improve completeness.

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%; description adds minimal extra context beyond schema (e.g., 'official GitHub template'). DryRun hint already present in 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?

Description clearly states it creates a new project skeleton from official eGovFrame template with specified settings. However, it does not explicitly differentiate from sibling tools like add_egovframe_components or validate_egovframe_project.

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?

Only mentions using dryRun=true for preview. No guidance on when to use this tool versus alternatives, prerequisites, or when not to use it.

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