QuantConnect

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

Annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds that it 'estimates' execution time, which aligns with the read-only nature. However, it doesn't provide additional behavioral context such as whether this is a quick approximation versus a detailed simulation, what factors influence the estimate, or any rate limits or prerequisites. The description doesn't contradict annotations but adds minimal value beyond them.

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 extremely concise - just one sentence that directly states the tool's purpose. There's no wasted language or unnecessary elaboration. However, given the complexity of the tool, this brevity comes at the cost of completeness, making it somewhat under-specified rather than optimally concise.

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?

For a complex optimization estimation tool with 0% schema description coverage, no output schema mentioned in context signals (though the prompt says 'Has output schema: true'), and rich nested parameter structures, the description is severely inadequate. It doesn't explain what the estimation returns, how accurate it might be, what factors affect the estimate, or how this fits into the broader optimization workflow. The existence of an output schema helps, but the description itself provides insufficient context.

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 input schema has 0% description coverage, meaning parameter documentation is entirely missing from structured fields. The description only mentions 'specified parameters' without explaining what those parameters are or their significance. For a complex tool with nested optimization configuration objects, this leaves the agent with no semantic understanding of what inputs are required for a meaningful time estimate.

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 states the tool 'estimates the execution time of an optimization with the specified parameters', which provides a clear verb ('estimate') and resource ('optimization execution time'). However, it doesn't distinguish this from sibling tools like 'create_optimization' or 'read_optimization', leaving the specific role of this estimation tool ambiguous within the optimization workflow.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention whether this should be used before creating an optimization, after configuring parameters, or in what context this estimation is valuable. With sibling tools like 'create_optimization' and 'read_optimization' available, there's no indication of this tool's specific use case in the optimization lifecycle.

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