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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not state whether the tool is read-only, mutating, or what side effects occur. It mentions 'Open Lab' which could imply a UI action, and 'same dump' which hints at output format, but nothing about permissions, reversibility, error handling, or return value. The description is completely opaque about behavior beyond the parameter's error note.

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 cryptic sentence that is not front-loaded with the core purpose. It uses jargon ('@R#', '@B#', 'dump') that is undefined, making it under-specified rather than concise. A concise description would clearly state the action and scope; this one obscures it.

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 tool with one parameter and no output schema, the description is severely incomplete. It does not clarify what the tool returns (presumably a list of iterations), how the output relates to 'Live rules', or when to invoke it. The lack of a clear purpose and behavior makes it inadequate for an agent to call correctly.

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%, and the parameter description for strategy_id is detailed: it explains routing to a Lab tab and the NO_ACTIVE_LAB error with a direct URL. This is strong schema-level documentation. The tool description itself adds no additional meaning about the parameter, so baseline 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 'Open Lab @R# rows as the same dump as Live rules' is cryptic and does not clearly state the tool's purpose. The verb 'Open' suggests navigation rather than listing, and the tool name 'list_iterations' implies listing iterations, but the description never mentions listing or retrieval. It references specific fields (parent, headline @B#, Long/Position/Exit) but without context. This is vague and not a clear statement of what the tool does.

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 guidance is provided on when to use this tool versus siblings like select_iteration or list_backtests. The description does not mention any conditions, prerequisites, or exclusions. The parameter description hints at routing to a Lab tab, but that's not usage guidance. There is no mention of alternatives or when this tool is preferred.

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