springBootStop

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

With no annotations provided, the description adds value by explaining the graceful shutdown mechanism (actuator first, then SIGTERM). However, it does not disclose potential side effects, idempotency, or state requirements, which would be beneficial for a destructive operation.

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 sentence with 10 words, front-loading the key action and strategy. No unnecessary information is included.

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?

Given the tool's action and lack of annotations/output schema, the description is too minimal. It omits essential context such as the meaning of the 'module' parameter, expected application state, and whether the tool is idempotent or safe to call multiple times.

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 only parameter, 'module', is not mentioned in the description, and the schema provides no description. With 0% schema description coverage, the description should compensate but fails to add any meaning beyond the schema.

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 tool's purpose: to stop a Spring Boot application gracefully. It specifies the shutdown strategy (actuator shutdown first, then SIGTERM), and distinguishes from sibling tools like springBootRestart and springBootRun.

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 usage for gracefully stopping a Spring Boot app but does not explicitly state when to use this tool versus alternatives like springBootRestart or when not to use it. No prerequisites or context are provided.

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