neon3_app_init

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

The description discloses that files are written only below NEON3_APP_ROOT, which is a valuable safety boundary. However, it omits other behavioral traits such as overwrite semantics, whether it creates directories, or what happens if the destination already exists. With no annotations, this is a partial disclosure.

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, front-loaded sentence that immediately conveys the core action. Every word contributes: bounded, Python or Node, and the root restriction. No filler.

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?

Without annotations or output schema, the description is all an agent has. It covers the basic operation but omits critical context such as how overwrite behaves, the relationship between destination and NEON3_APP_ROOT, and what the template contains. This is insufficient for reliable invocation, especially since two parameters are required.

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 0%, so the description must explain parameters. It references 'Python or Node' which maps to the runtime enum, and 'NEON3_APP_ROOT' hints at destination scope, but it doesn't clarify the destination parameter or the overwrite flag. The overwrite behavior is entirely undocumented, leaving the agent uncertain how to set it.

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?

Clearly states it creates a Neon3 application template with a specific verb and resource. The 'bounded' qualifier and mention of Python/Node scope it relative to sibling tools like neon3_project_assets or neon3_app_run. Distinct enough that an agent can identify its role.

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?

No guidance on when to choose this tool over siblings. It does not mention alternatives or conditions, such as when to use neon3_project_assets or neon3_app_run. The only implied usage is when initializing an app, but this is not explicit.

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