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

With no annotations, the description carries the behavioral disclosure burden. It does well by disclosing the response shape, the empty-payload case, the auth requirement, the Bearer token forwarding, and the fact that the payload is decrypted. It does not mention error behavior or rate limits, but for a simple GET-like read operation the provided detail is strong.

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 compact and front-loaded with the core purpose, then adds response shape, auth requirements, and configuration guidance. Each sentence contributes useful information without repetition or filler. It is appropriately sized for the tool's complexity.

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?

For a tool with no annotations and no output schema, the description covers the essential invocation details: purpose, auth requirement, source endpoint, response shape, and config preferences. It could be more complete by explicitly mentioning the required connection.host and clarifying that the operation is read-only, but overall it gives an agent enough to invoke it correctly.

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 reported as 0%, so the description must compensate. It explicitly explains auth.sessionToken and gives purpose to connection.workspaceName and connection.appId, but it does not clarify connection.host or the empty body/query/params containers. The description adds meaning beyond the schema for some parameters but not all.

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 verb and resource: it returns the decrypted session payload for the current authenticated session token. It also includes the source endpoint, which helps identify the operation. However, it does not explicitly differentiate itself from sibling tools like get_sessions_my or get_sessions_identity, so the distinction is somewhat implicit.

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 description provides useful context: it requires auth.sessionToken and explains how it is forwarded as a Bearer token. It also advises preferring connection.workspaceName and connection.appId as stable config. However, it does not state when to choose this tool over sibling session-related tools, nor does it give exclusions or alternatives.

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