detect_selenium_boot

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

No annotations provided, so description carries full burden. It discloses the detection mechanism (file lookup walking up parent directories) and that it returns a boolean 'detected'. Lacks detail on edge cases or errors, but sufficient for a simple detection 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?

Two sentences, no fluff. Each sentence adds critical information: what it does and how to use the result.

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?

Low complexity tool with one optional param and no output schema. Description covers purpose, detection method, output interpretation, and usage context. No missing aspects.

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?

Single parameter 'project_dir' with 100% schema coverage. Description adds that it defaults to the server's working directory, which is useful context 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 it detects if the current directory is inside a Selenium Boot project by looking for specific files (selenium-boot.yml or dependency). It also specifies the exact context: call before generating Java code. This distinguishes it from siblings like generate_java_junit5 etc.

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?

Explicitly says 'Call this BEFORE generating Java code' and gives conditional guidance: if detected=true, use framework='selenium_boot'. This tells the agent when and how to use the result.

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