init_gene

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the creation side effect (directory, phenotype.json template, starter files), but it does not mention permissions, overwrite behavior, authentication needs, or failure modes for a filesystem-mutating operation.

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 three sentences, front-loaded with the core action and followed by concrete details about output and fidelity options. It is efficient and wastes little space, though the final sentence is somewhat parenthetical.

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?

For a project-creation tool with no annotations and no output schema, the description covers the basic action and generated files, but omits important operational context such as authentication requirements, overwrite behavior, and default project location. It is minimally adequate but has clear 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 description coverage is 100%, so each parameter is already documented in the input schema. The description only repeats the fidelity types and creation target, adding no syntax, constraints, or meaning beyond what the schema provides; 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?

States a specific verb and resource: 'Initialize a new Rotifer Gene project.' It also explains what gets created (directory with phenotype.json template and starter files) and names the supported fidelity types. It does not explicitly differentiate from siblings such as create_agent or install_gene, but the purpose is clear.

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 wording implies usage for creating a new gene project, but there is no explicit when-to-use guidance, no when-not-to-use condition, and no named alternatives among the many sibling tools. Usage must be inferred from context.

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