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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it performs no build/run/scan side effects itself, and it guarantees the access key is never emitted — a meaningful security disclosure for a tool whose output is instructions containing tunnel setup steps.

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 sentences, no filler; the core purpose is front-loaded and the second sentence adds only the two constraints that matter (no execution, no access key). 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?

With no output schema, the description must convey what is returned, and it does — step-by-step build/serve/tunnel instructions. It also covers the relationship to the downstream scan tool and the scope limits, which is everything an agent needs to call and use it correctly.

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% and all three parameters (port, codebasePath, customBuildCommand) carry their own descriptions, so the schema does the heavy lifting. The description adds no parameter-level detail such as port/range constraints or how customBuildCommand interacts with the default build — 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 output ('Returns step-by-step instructions to build and serve a local web app and open a LambdaTest tunnel'), and explicitly disclaims doing the building, running or scanning itself. It also names the sibling tool (analyzeAppViaTunnel) that consumes the result, so it is distinguishable from siblings without opening a 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?

The description makes the workflow ordering explicit: this tool produces instructions so accessibility 'can then be scanned with analyzeAppViaTunnel', which tells the agent where it sits relative to that sibling. It doesn't state when to prefer this over, say, analyzeHyperExecuteJob or direct uploads, but the sequencing context is clear and actionable.

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