poll_rodin_job_status

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 thoroughly discloses return behavior, status values per mode, failure conditions, and the polling rule. This is excellent transparency for a status-checking tool.

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 organized by mode and front-loaded with the purpose, but it repeats the polling instruction almost verbatim for both modes. This redundancy makes it less concise than it could be, though it remains scannable.

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 two-mode polling tool with no output schema and no annotations, the description covers parameters, status values, and completion semantics for both modes. It omits edge cases like error handling or retry timing, but these are not essential for a basic status check.

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 schema has two undocumented parameters (0% coverage). The description compensates by explaining that subscription_key and request_id come from the generate step and mapping each to the appropriate mode. It doesn't explicitly state that exactly one is required or that they are mode-specific, but it adds significant meaning.

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 clearly states the tool checks whether a Hyper3D Rodin generation task is completed, with specific verb 'Check if' and resource. However, it doesn't explicitly differentiate itself from similar status tools like get_hyper3d_status, so it's clear but not fully distinguished.

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?

The description gives clear usage context: it is a polling API to use after a generate step, and it instructs when to proceed (only when status is final). It does not mention alternatives or exclusions, but the context is strong enough for an agent to know when to call it.

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