Get a journey run by id

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

Describes polling behavior and what information is returned, but with no annotations, it falls short on safety, idempotency, or rate limits. 'Pro+' hints at paid tier but not explained.

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?

Single sentence is concise and front-loads the tool's core function, but lacks structural elements like line breaks or separate usage notes.

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?

No output schema, so description must detail return value, but only mentions vague 'per-step checkpoints' and 'failure reason'. Fails to specify format or content of checkpoints, leaving significant gaps for the agent.

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 0% and description adds no meaning to the required runId parameter beyond its type and format. The description fails to explain the parameter's purpose or constraints.

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?

Description clearly states it polls a run started by run_journey, returning per-step checkpoints and failure reason. Distinguishes from sibling tools like run_journey (starts runs) and get_run (generic run retrieval). The 'Pro+' hint adds context but is vague.

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?

Implies use after run_journey, but no explicit when-to-use versus alternatives. Lacks guidance on when not to use or which sibling to choose.

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