get_slurper_job

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

There are no annotations, so the description carries the full burden of behavioral disclosure. 'Get details' implies a read-only operation, but it does not describe what details are returned, whether the job must exist, error behavior, or any account-scoping requirements. For a simple GET-style tool this is minimal but still somewhat thin.

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, focused sentence with no filler. It front-loads the action and resource, making it easy to scan. 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?

For a straightforward two-parameter read operation, the description is adequate but sparse. There is no output schema, so the description should ideally say more about the returned details. Given the very large sibling list, a brief note clarifying that this retrieves a specific Slurper migration job would improve completeness.

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 schema already provides 100% coverage with descriptions for both job_id and account_id. The description adds no additional parameter semantics beyond what the schema supplies. With complete schema coverage, the baseline 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 states a clear verb and resource: 'Get details of a migration job.' It is distinct from its most relevant sibling, list_slurper_jobs, by signaling a singular detail retrieval. The term 'migration job' could be slightly ambiguous, but combined with the tool name it is understandable.

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 explicit guidance is provided on when to use this tool versus alternatives. It does not mention list_slurper_jobs or clarify that you should list jobs first and then call get_slurper_job with a specific job_id. The usage context must be inferred entirely from naming conventions.

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