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 meaningful behavioral context beyond annotations: the pagination-object caveat versus result_set.total, and the fact that logType 'instrumentation' returns XCUI and Espresso logs. It omits auth constraints and rate limits, so it is strong but not exhaustive.

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?

Front-loads the core purpose, then lists capabilities and caveats in a compact, information-dense paragraph. Every sentence earns its place: the resource enumeration, platform applicability, pagination warning, and sibling routing all add distinct value with no filler.

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?

Given 14 parameters, a multi-action dispatcher design, and no output schema, the description covers the essential call semantics: resource/action combinations, platform scope, logType behavior, and pagination handling. It does not describe return shapes for get/list operations or error behavior, but for a read-only query tool with rich schema coverage this is nearly complete.

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%, so the schema already documents every parameter, including required combinations and logType enums. The description reinforces useful relational semantics—every resource/action combination works on web or app, and logs require a logType—but adds little syntax or format detail beyond what the schema provides. 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 resource family: 'Read-only query of LambdaTest automation resources', then enumerates the exact reads it covers (builds, sessions, tests, logs). It distinguishes itself from mutation siblings by explicitly naming updateBuild, stopBuild, and deleteBuild, so an agent can tell it apart without inspecting schemas.

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?

Provides clear when-to-use context: read-only automation queries across web and app, with explicit exclusions for build mutations (updateBuild, stopBuild, deleteBuild). However, it does not distinguish itself from specialized log-retrieval siblings like getAutomationTestCommandLogs or getSessionV2CommandLogs, leaving overlap unresolved.

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