detect_bearing_faults

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

With no annotations, the description discloses a limitation (weak signatures) but lacks details on return values, side effects, or detection confidence.

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 concise with three sentences, front-loaded with the purpose, and no wasted words.

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 output schema exists and parameter descriptions are complete, the description is adequate but lacks details on detection criteria or required inputs beyond spectrum_id.

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 coverage is 100%, so the baseline is 3; the description adds no additional meaning beyond the physical mechanism, which is already implied by the context.

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 detects bearing defect signatures in the stator-current spectrum, distinguishing it from siblings like detect_broken_rotor_bars or compute_bearing_frequencies.

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 notes that bearing signatures are weak and suggests envelope analysis or vibration, implying when the tool might be limited, but does not explicitly specify when to use this tool over other detect_* tools.

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