create_backtest

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

The description only states that it creates and returns an ID. Annotations declare it non-destructive, but no additional behavioral traits are disclosed, such as side effects, speed, or dependencies.

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 a single 13-word sentence, front-loaded with the action. It is appropriately concise and wastes no words.

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?

The description lacks context about the required inputs and the overall workflow. For a creation tool that depends on a compile and project, it would benefit from mentioning these dependencies.

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?

The description does not mention any of the required parameters (projectId, compileId, backtestName) or the optional parameters object. Since the schema coverage is 0%, the agent receives no verbal guidance on what input is needed.

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 ('Create a new backtest request') and the outcome ('get the backtest Id'), distinguishing it from sibling tools like update_backtest or list_backtests.

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 usage context is provided; there is no guidance on when to create a backtest versus update or list, nor any prerequisites like requiring a compileId.

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