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

Description adds detail beyond annotations: specifies what is returned (status, time, portfolio, positions, orders) and confirms it does not advance the run. Annotations already mark readOnlyHint=true, but description enriches with concrete output.

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 with zero wasted words. First sentence packs the core purpose and output, second sentence adds use case. Ideal conciseness.

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 low complexity (1 param, no output schema, simple read operation), description fully covers what the tool does, what it returns, and when to use it.

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 clear description for run_id. Description does not add extra parameter information, but baseline 3 is appropriate as schema already serves the purpose.

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?

Clearly states the tool returns run state (status, simulator time, portfolio, positions, orders) and emphasizes it is read-only and does not advance the run. Distinguishes from sibling tools like step_run or advance_until_next_session.

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?

Explicitly states it is for resuming or monitoring an in-progress run. Implies when to use but does not explicitly exclude alternative scenarios like advancing or starting runs. Still effective given context.

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