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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It states that results are 'simulated,' which hints at a read-only operation, but it does not mention assumptions, data source, simulation horizon, or whether the operation is side-effect-free. Key behavioral context is missing.

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, front-loaded sentence that names the action, the subject, and the key outputs. It is efficient with zero fluff, making it easy for an agent to parse quickly.

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?

While the description names the return metrics, it does not specify the structure of the output (e.g., whether they are numbers, objects), nor does it mention error handling or assumptions about the simulation. Given the lack of an output schema, this is a notable gap. The description is adequate for a simple simulation but leaves some operational details ambiguous.

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 100%, so the schema already documents all three parameters (tickers, weights, initialCapital) with basic explanations. The tool description adds the phrase 'quantitative portfolio allocations' which contextualizes the parameters, but it doesn't elaborate on weight constraints or expected formats beyond what the schema states. Since coverage is high, the baseline of 3 is appropriate.

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 a specific verb ('Evaluate') and a clear resource ('quantitative portfolio allocations'), and explicitly names the three output metrics (Sharpe ratio, win rate, max drawdown). This makes the tool's purpose unambiguous and distinct from the sibling tools, which focus on stock analysis, strategy evaluation, or agent management.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention that this is for testing hypothetical allocations, nor does it contrast with related tools like evaluate_tsunami_strategy or analyze_stock_ai. The agent is left to infer the intended use case from the description alone.

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