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

Adds real behavioral context beyond annotations: that app automation sessions return a not-found error and which sibling carries app-session media. Annotations already declare readOnly/openWorld=false, so the description's job is smaller, but it could still note log retention, size limits, or completeness of the live log.

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 tightly packed sentences with the core capability front-loaded, immediately followed by the platform restriction and the alternative. 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 one parameter, no output schema, and annotations covering the safety profile, the description is nearly complete for correct invocation. The remaining gap is output shape (log format, truncation), which is minor for a read-only retrieval tool.

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 the single sessionId already documents the accepted ID format (DA-WIN-... or session ID). The description adds no format or identifier nuance beyond that, so 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?

Specific verb+resource ('Retrieve the request and response log of a test session') with explicit scope ('while it runs or after it ends'). It explicitly distinguishes itself from mobile siblings by restricting to web automation and pointing app-session consumers to listMobileSessions.

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?

States the exact when: web automation (Selenium, Playwright, Cypress) only, and the when-not: app automation returns not found, with the alternative listMobileSessions called out for video/screenshots. This is explicit routing, not inference.

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