delimit_loop_status

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

Declares 'Side effects: read-only' and specifies the underlying call, which is important behavioral context. No annotations exist, so the description carries full burden. It could mention auth or rate limits, but for a read-only check this is sufficient.

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?

Extremely concise: one line for purpose, then clear usage blocks, sibling contrast, and side effects. Every sentence is meaningful with no fluff.

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?

Given an output schema exists, the description provides sufficient context for a simple read-only metric tool. It covers purpose, usage, and side effects comprehensively.

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 the parameter description in the description mirrors the schema exactly. Baseline 3 is appropriate since the description adds no new semantic information beyond the schema.

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 uses a specific verb 'check' and specifically states 'autonomous loop metrics for a session (Pro)'. It clearly distinguishes from siblings by contrasting with delimit_loop_config and delimit_build_loop.

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?

Explicitly states when to use (inspect run-time metrics like iterations, cost, errors, safeguard status) and when NOT to use (configuring or running the loop), with exact sibling tool names.

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