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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds that the app must be local and tunneled, but says nothing about whether the analysis is synchronous, whether a status poll (e.g. checkAppProcessingStatus) is needed, or what triggers the scan.

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 key scoping qualifier ('locally running', 'via tunnel') front-loaded. Nothing is wasted, though it is arguably too terse to carry the workflow context an agent needs.

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 should clarify what the call yields (e.g. a scan/report id) and whether further steps are required. It leaves the completion path implicit despite the presence of related siblings like checkAppProcessingStatus and getAccessibilityScanReport.

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, tunnelId, tunnelName) are self-explanatory and documented in the schema. The description adds no extra meaning beyond what the schema provides, 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?

States a specific verb (Analyzes), the resource (a locally running app), the goal (accessibility), and the transport (via LambdaTest tunnel). It is clear about what it does, though it does not explicitly contrast itself with nearby siblings such as buildLocalAppForAnalysis or getAccessibilityReport.

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 'locally running app ... via LambdaTest tunnel' implies the preconditions (an app served on a local port reachable through a tunnel), but there is no explicit when-to-use vs when-not guidance or named alternative for already-uploaded apps.

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