whodb_platform_transform_wait

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds that this is a bounded polling wait, but the default timeout/poll values it alludes to are already in the schema, and it says nothing about what happens on timeout expiration.

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?

Three short sentences, front-loaded with the core action, followed by the precondition and the targeting rule. No filler; 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, the description should describe what a completed wait returns (final status, error surface on timeout). It states the target states but not the return shape or timeout behavior, leaving a moderate gap for an agent that must act on the result.

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%, so the base is 3. The description clarifies that run_id comes from whodb_platform_action and that workspace targets a single call without changing defaults, but the latter is already stated in the schema, so the added meaning is marginal.

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 (wait), resource (hosted transform run), and outcome (success or failure). The 'real hosted' qualifier implicitly distinguishes it from a preview/simulated path, though it does not name the analogous sibling whodb_platform_function_wait.

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?

Tells the agent to use the run id returned by whodb_platform_action and to keep the timeout bounded, giving a clear trigger and a practical guardrail. It lacks an explicit when-not (e.g., don't poll when you only need the run record), so it falls short of a full 5.

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