`@Schema` constraints silently ignored on method parameters

Bug description

@Schema constraint attributes (minimum, maximum, allowableValues, pattern, example) are silently ignored when placed on @Tool method parameters. Only description and requiredMode/required are read from parameter-level @Schema annotations. The constraints are absent from the generated JSON schema with no error or warning.

Environment

• Spring AI version: 1.1.4
• Java version: 21

Steps to reproduce

1. Annotate a @Tool method parameter with @Schema constraints:

@Service
public class ChanceTool {
    @Tool(name = "set_chance", description = "Set the chance value")
    public String setChance(
        @Schema(description = "Chance percentage", minimum = "0", maximum = "100")
        int chance
    ) {
        return "Chance set to " + chance + "%";
    }
}

2. Inspect the generated input schema (e.g. via tools/list MCP call or by calling JsonSchemaGenerator.generateForMethodInput directly).

3. Observe that minimum and maximum are absent from the chance property.

Expected behavior

The generated schema for chance should include the constraints:

{
  "properties": {
    "chance": {
      "type": "integer",
      "description": "Chance percentage",
      "minimum": 0,
      "maximum": 100
    }
  },
  "required": ["chance"]
}

Minimal Complete Reproducible example

import com.fasterxml.jackson.databind.JsonNode;
import com.fasterxml.jackson.databind.ObjectMapper;
import io.swagger.v3.oas.annotations.media.Schema;
import org.junit.jupiter.api.Test;
import org.springframework.ai.util.json.schema.JsonSchemaGenerator;

import java.lang.reflect.Method;

import static org.junit.jupiter.api.Assertions.assertNotNull;
import static org.junit.jupiter.api.Assertions.assertEquals;

class JsonSchemaGeneratorParameterSchemaTest {

    static class ChanceTool {
        public String setChance(
            @Schema(description = "Chance percentage", minimum = "0", maximum = "100")
            int chance
        ) {
            return "Chance set to " + chance + "%";
        }
    }

    @Test
    void schemaConstraintsOnMethodParametersAreReflectedInGeneratedSchema() throws Exception {
        Method method = ChanceTool.class.getDeclaredMethod("setChance", int.class);
        String schema = JsonSchemaGenerator.generateForMethodInput(method);
        JsonNode chanceNode = new ObjectMapper().readTree(schema).get("properties").get("chance");

        // description is correctly picked up
        assertEquals("Chance percentage", chanceNode.get("description").asText());

        // These fail, minimum and maximum are absent from the generated schema
        assertNotNull(chanceNode.get("minimum"), "expected 'minimum' in schema but was absent");
        assertNotNull(chanceNode.get("maximum"), "expected 'maximum' in schema but was absent");
    }
}

Start with JsonSchemaGenerator.generateForMethodInput and the provided JsonSchemaGeneratorParameterSchemaTest, then trace how parameter-level @Schema annotations are converted into the generated JSON schema. Done means the test verifies minimum and maximum, with the other listed constraint attributes represented as applicable.