initialize_project

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

No annotations are provided, so the description must disclose behavior. It mentions initialization at a path and the two strategies (fpm or Makefile), but does not specify side effects like overwriting existing files, error conditions, or permissions requirements. Some behavioral traits are implied but not fully transparent.

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, information-dense sentence. It is front-loaded with the core purpose and efficiently communicates the key behavioral choice. 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?

Given the three parameters and presence of an output schema, the description covers the essential functionality. It explains the high-level behavior and method selection. However, it omits details like whether a subdirectory is created or if version control is initialized, which could be inferred but are not explicit.

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 the baseline is 3. The description does not add additional meaning beyond the schema; it restates project path and name and mentions Fortran version only implicitly via 'modern Fortran'. No new parameter context is provided.

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 the tool initializes a new Fortran project, specifying the method (fpm or Makefile). It distinguishes from sibling scaffolding tools like scaffold_hpc_grid and scaffold_unit_test by focusing on general project setup.

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 use for new Fortran projects, but lacks explicit when-to-use or when-not-to-use guidelines relative to siblings. It mentions fpm availability, which helps decision-making, but no exclusions or alternatives.

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