Check a 37Soul operation

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

No annotations are provided, so the description carries the full burden. It usefully discloses the asynchronous lifecycle (queued/running vs. final result), but says nothing about whether the call blocks, what it returns while the operation is still pending, how failures are surfaced, or whether polling is rate-limited.

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?

Two sentences, zero filler, with the core behavior front-loaded and the prerequisite (where the operation_id comes from) placed second. Every clause earns its place.

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 and no annotations, the description should say more about the return shape of a polled result (pending vs. completed vs. failed). The lifecycle framing is helpful, but an agent still cannot tell what a response looks like or how to react to a still-running operation.

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 single parameter's schema description already states it is the id returned by chat_with_host or instruct_post. The description repeats that provenance rather than adding format, range, or lookup semantics beyond it, so the baseline of 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 resource ('Check the final result of a chat or post operation') and scopes it to operations that are 'still queued or running', which cleanly separates it from the synchronous siblings chat_with_host and instruct_post that create those operations. An agent can identify the tool's role without opening the schema.

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 the triggering condition (an operation is queued or running) and where the required argument comes from ('the operation_id returned by chat_with_host or instruct_post'), which is exactly the context needed to invoke it. It lacks an explicit when-not or guidance on repeated polling, so it stops short of a 5.

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