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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description does add useful output-behavior context (percentile band by year, deepest drawdown, the mix's historical return/volatility, and a compoundsim.app link reproducing the scenario), but says nothing about cost, expected runtime, or whether the simulation is stochastic/non-deterministic between calls — a notable omission for a Monte Carlo tool.

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?

A single sentence, front-loaded with the method and scenario, then the return payload, then the link. It is long but every clause carries information; only the URL clause is arguably optional.

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 no output schema, the description correctly takes on the burden of describing returns (percentiles by year, max drawdown, historical stats, shareable URL), which is exactly what an agent needs to report results. It omits assumptions that matter for interpretation, such as how non-USD currency paths are modeled, though the schema covers that in the currency field.

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% and every parameter carries a detailed description (asset ticker meanings, preset compositions, history spans, inflation semantics), so the schema does the heavy lifting. The prose only echoes the optional starting sum and the asset-vs-mix choice, adding no syntax or constraint detail beyond the schema; baseline 3 applies.

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?

States a specific verb and method (Monte Carlo simulation) applied to a specific resource (monthly investing in one asset or a monthly-rebalanced mix), including the optional lump sum. It does not explicitly name or distinguish itself from siblings like compare_portfolios or simulate_withdrawal, but the monthly-accumulation framing is distinctive enough to separate it from a fixed-rate or withdrawal simulation.

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 implies the scenario (accumulating via monthly contributions, with or without a starting sum) but gives no explicit when-to-use / when-not-to-use guidance and never names an alternative. An agent must infer that compare_portfolios is the choice for comparing multiple mixes rather than simulating one.

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