generate_service

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

With no annotations, the description must disclose side effects and behavior, but it only says 'following best practices' and 'with interface and implementation.' It omits critical details such as file creation/overwrite behavior, naming conventions, dependencies on an existing entity/repository, or whether the generated code compiles. This is a significant transparency gap for a tool that mutates the filesystem.

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, concise sentence that front-loads the core action and resource, with no filler or redundant phrasing. It is appropriately sized for a tool with schema-covered parameters.

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 tool generates code and has no output schema, but the description does not explain what the generated files look like, what conventions are applied, or what the tool returns. It relies on the phrase 'following best practices' without specifying any concrete behavior, leaving the agent without enough context to anticipate the outcome beyond the abstract purpose.

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 provides 100% coverage for all five parameters with descriptions and defaults, so the schema does the heavy lifting. The tool description itself adds no additional parameter meaning beyond what the schema already states, meriting the baseline score.

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 specifies the action ('Generate'), the resource ('Spring Boot Service'), and the structural detail ('interface and implementation'), which distinguishes it from sibling tools like generate_entity or generate_controller. It leaves no ambiguity about what the tool produces.

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 provides clear context: this is for generating a Spring Boot service layer, implying you use it when you need a service with interface and implementation. It does not explicitly mention alternatives or when not to use it, but the sibling tool names and the specific resource make the usage context reasonably clear.

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