run_backtest

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

The description discloses blocking behavior (wait flag), timeout, and portable flag. It mentions that wait requires ShutdownTerminal=1 in the ini file. However, with no annotations, it lacks details on side effects, permissions, or return value semantics.

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 concise with a brief intro, bulleted args, and return values. It's front-loaded with the main purpose. It could be slightly more structured (e.g., grouping return fields), but overall efficient.

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?

With 4 parameters, no output schema, and no annotations, the description covers purpose, args, and return. It lacks error handling, prerequisites, and relationship to sibling tools, but is adequate for basic usage.

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 0%, but the description adds meaning: config is absolute path, wait blocks until exit, timeout_sec is wait timeout, portable passes the /portable flag. This significantly compensates for the schema's lack of descriptions.

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 it launches a terminal with a tester.ini config to run backtests. The verb 'Launch' and resource 'terminal with /config:<tester.ini>' are specific, but it doesn't explicitly distinguish from related tools like 'start_job' or 'compile'.

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?

No guidance on when to use this tool versus alternatives like 'start_job' or 'smoke_test'. The description only explains what it does without providing context for selection.

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