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

The description reinforces the readOnlyHint annotation with 'Read-only; never mutates session state,' and adds behavioral nuance beyond annotations by warning that the session_id token suffix is a credential and should never be stripped. This provides useful operational context without contradicting the structured hints.

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?

The description is slightly long but well-organized, starting with a bolded 'INSPECTION' header and using bullet-like lines for related tools. Each sentence provides distinct value—scope, return content, companion tools, and usage trigger. It is front-loaded and structured for quick scanning, though it could be trimmed slightly without losing meaning.

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 there is no output schema, the description thoroughly explains return values: 'full message history (user / assistant / tool turns) plus the session's meta — workflow step, cloud, deployment status, drift state.' It also covers required input format, usage context, and read-only behavior, making the tool fully understandable without external documentation.

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 100% with a clear pattern and description for session_id. The description adds extra meaning by explaining the token suffix is part of the session credential and must be preserved, which is critical for correct invocation. While the schema already documents the format, the description elevates the parameter's semantic importance.

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?

The description clearly states the tool's function: 'View a session's conversation transcript and metadata' with a specific verb and resource. It explicitly distinguishes itself as 'the transcript-reader companion to the other read tools' and lists sibling tools for alternative use cases, making it easy to select correctly.

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 explicit when-to-use guidance: 'Use it when a user asks 'what did I say earlier?' or you need to retrace why the session ended up where it did.' It also names alternatives (convostatus, tfruns, stackversions) for other intents and states it is read-only, giving clear selection criteria.

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