List Stem Jobs

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

With no annotations, the description discloses that output URLs are excluded, which is a key behavioral trait. However, it omits authentication requirements, default pagination, or ordering 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?

Two concise sentences front-load the purpose and quickly add a critical caveat, containing no superfluous information.

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?

Given no output schema or annotations, the description covers the basics but does not specify response format, defaults, or limitations, leaving gaps for a complete understanding.

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 description maps parameters to functionality (status filter, pagination with limit/offset) but lacks detailed semantics like enum meanings or default values, partially compensating for 0% schema coverage.

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 lists the authenticated user's recent stem jobs with optional filtering and pagination, and distinguishes itself from sibling tools like get_job and source-specific list tools.

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 explicitly advises using get_job for output URLs, providing clear guidance on when not to use this tool. However, it does not contrast with list_soundcloud_jobs or list_youtube_jobs.

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