list_inference_recommendations_jobs_sagemaker

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

With no annotations provided, the description carries the full burden, but it only states 'List all...' without disclosing behaviors such as pagination, response structure, or potential side effects. While 'List' implies a read-only operation, no additional behavioral context is given, leaving gaps about how the tool actually behaves.

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 unnecessary words. It directly and efficiently states the action and the resource.

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 simple zero-parameter list tool with an output schema, the description is largely complete. However, it does not mention pagination or whether 'all' jobs requires multiple calls, which could be relevant to an agent. Since the output schema is present, return value details are covered elsewhere.

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 tool has zero parameters, so the description is not required to explain parameter syntax or semantics. According to the rubric, a zero-parameter tool receives a baseline score of 4.

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 uses the specific verb 'List' and clearly identifies the resource as 'SageMaker Inference Recommender Jobs', distinguishing it from sibling tools like list_training_jobs_sagemaker and list_inference_recommendations_job_steps_sagemaker. The purpose is unambiguous.

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 its usage through 'List all', but it does not provide explicit guidance on when to use this tool over alternatives, such as list_inference_recommendations_job_steps_sagemaker. There are no exclusions or additional context to clarify the exact scenario.

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