Get Workflow Session

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

Annotations already provide readOnlyHint=true and idempotentHint=true, telling the agent this is a safe, read-only, idempotent operation. The description adds the verb 'Read', which is consistent but does not add further behavioral details (e.g., behavior when sessionId is invalid). With annotations covering the key traits, the description provides minimal incremental value.

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?

A single sentence that directly states the tool's purpose with no unnecessary words. It is front-loaded with the verb and resource, making it highly efficient for an agent to parse.

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 the tool's low complexity (single parameter, no output schema, and strong annotations), the description provides sufficient information. It covers the essential action and resource, and the annotations fill in safety and idempotency. No additional context is necessary for correct invocation.

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% as the only parameter (sessionId) is described in the schema. The description does not add meaning beyond stating that retrieval is 'by id'. It does not clarify format, constraints, or relationship to other fields. Baseline 3 is appropriate since schema already documents the parameter.

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 action ('Read') and the resource ('persisted GenLayer workflow session by id'). It distinguishes this tool from sibling tools like genlayer_start_workflow_session (create) and genlayer_list_workflow_sessions (list), making the purpose unambiguous.

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 implies usage for retrieving a specific session by ID, which is clear from the context. However, it does not explicitly state when not to use it or suggest alternatives like genlayer_list_workflow_sessions for enumeration. The context is clear but lacks exclusions.

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