List SoundCloud Jobs

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

No annotations are provided, so the description carries full burden. It mentions 'recent' and optional filter/pagination, but lacks details on authentication requirements, rate limits, or behavior when no jobs exist. The description is adequate but not comprehensive.

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 a single efficient sentence that front-loads the action and resource. It is concise, though slightly under-specified for fully self-contained understanding. Every word 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?

Given the tool has 3 optional parameters, no required params, and no output schema, the description is incomplete. It does not explain return format, error handling, pagination behavior, or how to interpret results. More context is needed for successful 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 description coverage is 0%, so the description must compensate. It only generically mentions 'optional status filter and pagination' without explaining parameter semantics (e.g., meaning of each status enum, how limit/offset control pagination). Parameter names are self-explanatory but description adds minimal value.

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 action ('List'), resource ('the authenticated user's recent SoundCloud jobs'), and includes optional filters and pagination. It distinguishes from sibling tools like 'get_soundcloud_job' (singular) and 'list_jobs' (likely broader 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 implies usage for listing jobs with filters, but provides no explicit guidance on when to use this tool over siblings like 'list_jobs' or 'list_youtube_jobs'. No when-not-to-use or alternative recommendations are given.

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