springBootRun

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

No annotations are provided, so the description carries full burden. It mentions log capture and port detection, but does not disclose side effects (e.g., port binding, process management), blocking behavior (only partially via waitForStartup param), or cleanup requirements. This is insufficient for a startup tool.

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 very concise (two sentences) and front-loads the purpose. However, it could be slightly more detailed given the tool's complexity, so not a 5.

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 tool with 3 parameters, no output schema, and 19 siblings including lifecycle commands, the description omits critical details: return value, error states, preconditions (e.g., compiled project), and post-usage cleanup. This inadequately supports agent decision-making.

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?

Schema covers 100% of parameters with clear descriptions. The tool description adds minimal parameter-specific value (e.g., 'Captures logs' hints at waitForStartup's role). Baseline 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 clearly states the tool starts a Spring Boot application, captures logs, and detects port/startup. It effectively distinguishes from sibling tools like springBootStop, springBootRestart, and springBootLogs by focusing on startup behavior.

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 on when to use this tool vs alternatives (e.g., springBootRestart, runTests). The description implies use for starting the app, but lacks context on prerequisites or scenarios where other tools are more appropriate.

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