waveform_locate

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

With no annotations, the description carries the behavioral burden. It discloses the search strategy (running processes first, then well-known install locations), which is useful and not inferable from the schema or name. It does not mention failure behavior when the binary is not found, but the core non-mutating search behavior is conveyed.

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?

Three short sentences with no filler: the action and return value are front-loaded, followed by the search strategy and a clear usage directive. Every sentence earns its place.

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 simple, parameterless discovery tool with no output schema, the description is complete: it states what is found, what is returned, how the search proceeds, and when to call it in the broader workflow. No critical information is missing for an agent to invoke it correctly.

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 tool has zero parameters, so the schema already fully covers the parameter surface. The baseline for no-parameter tools is 4, and the description adds no misleading or unnecessary parameter detail.

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 uses a specific verb ('Find'), names a concrete resource (the installed Waveform binary), and states the output (the path). This clearly distinguishes it from sibling tools like waveform_launch, waveform_focus, and waveform_status, which have different responsibilities.

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 explicitly tells the agent when to run this tool: before launch/focus tools, so the rest of the chain has a path to use. It gives clear timing guidance but does not enumerate when not to use it or name explicit alternatives beyond the implied launch/focus siblings.

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