stream-job

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

The description explains polling behavior and terminal states, but lacks details on rate limiting, error handling, partial output on failure, or maximum polling duration. With no annotations, the description carries the full burden and is adequate but not exhaustive.

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 two sentences, front-loaded with purpose, and succinctly explains the polling mechanism and terminal states. No superfluous words.

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?

The description explains the polling process but does not clarify the return format (what chunks look like) or handle potential long-running behavior. Without an output schema, the description should provide more detail on expected return values, which is missing.

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 both parameters have clear schema descriptions. The tool description adds no new information about the parameters beyond what the schema already provides, so baseline score of 3 is appropriate.

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 retrieves streaming output from a Serverless job via polling until a terminal state, distinguishing it from siblings like get-job-status or run-endpoint. It specifies the action, resource, and scope.

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 mentions a prerequisite ('worker must support streaming output') and implies use for collecting all output until completion. However, it does not explicitly contrast with alternatives like get-job-status or note when not to use this polling approach.

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