neon3_app_test

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

With no annotations, the description carries the behavioral burden and does add useful traits: checks are deterministic, local, and make no live Neon3 service contact. However, it does not disclose possible side effects, failure behavior, or what the tool reports back.

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?

A single, front-loaded sentence with no filler or redundant phrasing. Every word contributes to the tool's core behavior, making it easy to scan.

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 test tool with no output schema and no annotations, the description should explain what a successful check looks like and how runtime, cwd, and timeout relate to execution. It gives good high-level context but lacks the invocation-level details an agent needs.

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 0% and the description names none of the three parameters. The parameter names and runtime enum are self-explanatory, but the description does not clarify what cwd should point to or how timeout_ms is applied to the checks.

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 states a clear verb ('Run') and resource ('deterministic local protocol checks') and includes a distinguishing qualifier ('without contacting a live Neon3 service'). This sharply differentiates it from siblings like neon3_app_run or live-service checks.

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 phrase 'without contacting a live Neon3 service' implies the offline/local testing context, but no alternative tools are named and no explicit when-not-to-use guidance is provided. The usage intent is inferable rather than stated.

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