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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds real domain behavior beyond that: the recursive account scope, the fact that only 'executed' status yields results, and that strategies are excluded, which are things an agent cannot infer from annotations or schema.

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 core scope statement is front-loaded and the follow-up sentences each add distinct information (definition, executed-status caveat, open_dashboard hand-off, strategy exclusion). The RST-style backticks and line breaks make it slightly more verbose than necessary but nothing is wasted.

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 carries the return-value burden and does so reasonably: it signals that entries have a status and that only 'executed' ones carry results. The main residual gap is guidance on how to obtain the required portfolio_id, which matters for a single-parameter tool.

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% with one required integer parameter, so the description must compensate. It partially does by conveying that portfolio_id denotes an account whose descendant accounts are also included, but it gives no hint about where to obtain a valid id or what the identifier format is (list_portfolios is never referenced).

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 names the resource (saved simulations) and scopes it to 'an account and the accounts under it', and it defines what a simulation is, which separates it from sibling concepts like strategies ('Strategies have no simulations'). The verb 'list' is only implicit, but the intent is unambiguous.

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?

It gives concrete routing guidance: only simulations with status 'executed' have results, and those should be passed with their account to open_dashboard for comparison. It also sets an exclusion boundary ('Strategies have no simulations'). There is no explicit statement of when to prefer a different listing tool, but the sibling set has no close alternative.

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