run_verification

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

With no annotations, the description carries the full behavioral burden. 'Allowlisted' hints at a security restriction but leaves key traits undisclosed: what happens when a command is not allowlisted, whether commands run sequentially or in parallel, mutation/execution risk, or the effect of cwd and timeout_ms.

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 tight sentence with the scope-defining examples placed up front and no wasted words. It is arguably terse to the point of under-specification, but structurally it is clean and front-loaded.

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 command-execution tool with no annotations, no output schema, and zero documented parameters, the definition is too thin. An agent lacks the operator/allowlist rules, return shape, and per-parameter semantics needed to invoke it confidently.

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% across three parameters (cwd, commands, timeout_ms), and the description mentions none of them. The names are largely self-explanatory, but nothing explains the accepted command vocabulary, the allowlist behavior, or timeout semantics to compensate for the coverage gap.

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 gives a specific verb (Run) and resource (verification commands), and the parenthetical 'test/lint/typecheck' pins down the scope precisely. No sibling tool overlaps with local verification, so sibling differentiation is not a concern, but the definition itself is clear and concrete.

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?

It never states when to run verification, what 'allowlisted' permits, or any prerequisites (e.g., that a project must exist in cwd). An agent must infer usage from the name alone, with no exclusions or alternative-tool routing given.

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