loop.read_iterations

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only contains the verb 'Read.' It does not explain whether the operation is side-effect-free, what exactly an 'iteration' is, what format the recorded data takes, or what the tool returns.

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 concise sentence with no wasted words and immediately communicates the core action. It is appropriately sized, although its brevity comes at the cost of informative context.

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 invocation is trivial with no parameters, the absence of an output schema and annotations means an agent must infer what 'recorded loop iterations' contains and how it relates to loop.record_iteration. The description is too thin to be fully contextual in the presence of related loop and flow tools.

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 tool has zero parameters and the input schema already documents this completely with an empty properties object. Since there are no parameters, the description does not need to provide additional parameter-level detail.

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 clear verb-resource pair: 'Read recorded loop iterations.' It is specific enough to avoid tautology and distinguishes the read operation from write-oriented sibling tools like loop.record_iteration, though it does not explicitly differentiate itself from loop.generate_report.

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 alternatives such as loop.record_iteration, loop.generate_report, or flow.read_memory. The verb 'Read' implies retrieval, but the description does not state the conditions that should lead an agent to select this tool.

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