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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description goes beyond them by disclosing the payload shape, including that steps carry playwright commands and signed screenshot URLs, which is the kind of detail an agent needs to decide whether to call it. It omits signed-URL expiry or size limits, so it is not fully transparent.

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, zero waste: what it does first, payload second, usage trigger last. Every clause carries distinct information.

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 correctly carries the return-value burden by listing the response fields, and annotations cover the read-only/idempotent profile. It is nearly complete for a single-param read, missing only edge behavior for an unknown or expired session id.

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 coverage is 67%; botId and projectApiKey are documented in the schema (including the auth caveat about get-bot-credentials/get-project-credentials), but manualSessionId has no schema description. The description only says 'by id', adding no format or provenance detail for the required parameter, so it does not compensate for the gap.

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 ('Fetch') and resource ('a manual test session by id'), then enumerates the returned content (project id, title, environment, steps, linked scenario ordinal ids). No sibling in the list covers manual sessions, so there is no ambiguity to resolve.

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?

'Use when authoring a SmartTest from a recorded manual session' gives a concrete trigger context rather than leaving usage implied. It stops short of naming an alternative or a when-not condition, which keeps it out of 5 territory.

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