stream-job

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

No annotations provided, but description discloses polling behavior and terminal states (COMPLETED, FAILED, CANCELLED, TIMED_OUT). Could add polling interval or timeout details.

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 sentences: starts with core purpose, then prerequisite, then technical detail. Efficient and well-organized.

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?

Lacks details on return format of chunks (e.g., raw bytes, JSON) and does not specify polling interval or timeout, leaving some ambiguity for a polling tool.

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 descriptions cover both parameters (endpointId and jobId) with patterns and descriptions. Description adds no additional parameter meaning beyond schema, so baseline score 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?

Clearly states it retrieves streaming output from a Serverless job via polling until terminal state. Differentiates from siblings like get-job-status (status only) and run-endpoint (launch).

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?

Mentions prerequisite 'worker must support streaming output' but does not explicitly state when to use or specify alternatives among sibling tools.

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