wave_value

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

With no annotations, the description carries the transparency burden. The verb 'Read' implies a non-mutating operation, and it discloses the wave_id condition, but it does not explain error behavior (e.g., if wave_id omitted with multiple waves) or any other side effects.

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 concise sentences cover the core purpose and key usage requirements without unnecessary detail. Front-loads the primary verb and object.

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 simplicity and the presence of an output schema, the description provides sufficient context for standard usage. It omits explanation of context_id and the 'typed' aspect of values, but these are not critical for operation.

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 description coverage is 0%, so the description must compensate. It adds meaning for times by giving a concrete unit-bearing example ('200ns') and explains when to set wave_id, but signals and context_id are left unnamed and unexplained.

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 opens with 'Read typed waveform values,' which clearly states the action (read) and the object (typed waveform values), distinguishing it from wave_manage (management) and wave_compute (computation). The mention of signals and times further specifies the scope.

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?

Provides clear usage context by specifying required inputs (signals, unit-bearing times) and a conditional parameter (wave_id when multiple waves are attached). Does not explicitly name alternative tools or exclusions, but the usage is well-contextualized.

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