list_slurper_jobs

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

With no annotations provided, the description carries the full behavioral burden, but it only restates the operation. It does not disclose pagination, response shape, ordering, or any other trait an agent would need to know beyond the basic list action.

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, front-loaded sentence with no filler, and the parenthetical adds useful terminology clarification. It is appropriately short for a simple single-parameter list tool.

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 schema covers the parameter, and the description gives the basic operation, so a basic call can be made correctly. However, with no output schema, no behavioral notes, and no alternative routing, the overall context is thin for an agent that needs to know what to expect from the response.

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 input schema already documents the only parameter, account_id, with 100% coverage. The description adds no additional meaning about how account_id is used or what scope it imposes on the listed jobs.

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 verb 'List' and the resource 'migration (slurper) jobs', and the parenthetical usefully explains the opaque 'slurper' term. It distinguishes itself from the get_slurper_job and get_slurper_job_progress siblings through the list/get contrast, though it does not explicitly describe the list's 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?

No guidance is given about when to use this tool versus get_slurper_job or get_slurper_job_progress. There is no use-case context, prerequisite mention, or scenario where the alternative should be preferred.

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