Computes forward or inverse Haar wavelet transforms on numeric arrays whose length is a power of two, supporting signal analysis and reconstruction.
Haar wavelet transform (forward and inverse) on a power-of-2 length array.
| Name | Required | Description | Default |
|---|---|---|---|
| values | Yes | Input values (length must be power of 2) | |
| inverse | No | Inverse transform (default false) |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the power-of-2 input constraint and inverse support, but omits return format, error behavior, and whether the operation is pure or out-of-place.
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?
Single front-loaded sentence with no wasted words. The size is appropriate for a simple mathematical transform tool.
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 pure transform with full parameter schema coverage, the description covers operation and input constraint. However, with no output schema, it omits return format and error behavior, leaving minor gaps.
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 100%, so the baseline is 3. The description repeats the power-of-2 constraint and forward/inverse nature but adds no syntax, format, or meaning beyond what the schema already provides.
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?
Names the specific transform, states forward and inverse support, and specifies the power-of-2 input constraint. Clear verb/resource, but it does not distinguish itself from mathematical-transform siblings such as fft_transform or wavelet_tree.
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 no when-to-use or when-not-to-use guidance and names no alternatives. The inverse flag implies direction, but no selection guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.