Install, lint, build and test

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

Annotations only supply destructiveHint=false, so the description must carry behavior, and it does add real value beyond that: fail-fast semantics ('stops at the first failure') and the fact that the failing step's output is returned. It still omits notable traits such as long runtime, network/package downloads, and that running install modifies the working directory.

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?

Two tight sentences with zero filler: the first front-loads the action and scope, the second states the failure/output behavior. Every clause earns its place.

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 tool with no output schema, the description does state that the failing step's output is returned, and it covers the parameter's role indirectly. It stops short of describing runtime expectations, side effects of installing dependencies, or what a successful run returns.

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?

There is one parameter with 100% schema description coverage ('Project folder (absolute path, or relative to the server's working directory)'), so the schema already fully documents it. The description adds no path syntax or resolution detail beyond what the schema states, which is the expected baseline.

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?

Names a specific verb ('run') and resource (the project's install, lint, typecheck, build and test steps), then enumerates the supported toolchains (npm, Python .venv/pytest/build, cargo clippy/build/test). This is enough to separate it from generic siblings like run_command, install_tool, and verify_install without opening any schema.

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?

Usage is implied: this is the whole-pipeline verification tool, so an agent can infer it is the one-shot 'check my project' call. However, no explicit when-to-use guidance or alternatives are named (e.g. run_command for a single command, install_tool or verify_install for narrower steps), so routing is left to inference.

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