poll_rodin_job_status

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

No annotations are present, so the description carries the full burden. 'Check if ... is completed' implies a read-only status query but says nothing about return values, polling semantics (blocking vs immediate), error cases, or mode-specific behavior.

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?

A single sentence that is front-loaded and contains no filler. It is appropriately compact for a simple status check, though it offers no additional structured guidance.

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 or annotations, agents need the description to clarify what the response looks like and how to identify a job. The description only says a task is completed/not completed; it doesn't state whether one of request_id or subscription_key is mandatory, how they correspond to FAL_AI vs MAIN_SITE modes, or what statuses exist. This is incomplete for reliable invocation.

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%; each parameter has a brief mode hint. The tool description adds no meaning beyond naming the task, so it doesn't help resolve the ambiguity of having two optional parameters with no required ones. Baseline 3 applies because the schema already documents them.

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 action (checking completion) on a specific resource (Hyper3D Rodin generation task), so an agent can infer the basic function. However, it does not differentiate from sibling get_hyper3d_status or poll_hunyuan_job_status, which likely serve similar status-checking roles.

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?

Provides no information about when to poll this status versus using get_hyper3d_status, or when to use request_id versus subscription_key. No exclusions or alternatives are named, leaving the agent to choose purely on the tool name.

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