add_spl_offset

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

The description notes 'changes the measurement in place', which discloses a key behavioral trait (mutation). However, with no annotations, it does not discuss reversibility, effects on derived data, or prerequisites. This adds some value but leaves several transparency gaps.

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?

A single, front-loaded sentence that is direct and free of filler. It earns its place by conveying the core purpose and in-place mutation without redundancy.

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 two-parameter mutation tool with no output schema, the description is mostly complete. It covers the purpose and the mutation behavior, but omits details like return value or preconditions (e.g., measurement must exist). Slight gap, but adequate for the tool's simplicity.

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% with concise parameter descriptions (offsetDb: 'negative to lower'; measurement: UUID vs index). The description adds no new semantic detail beyond the schema, so it does not improve upon the baseline.

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 action ('Shift a measurement's SPL level by a fixed offset in dB') and differentiates it from siblings like align_spl or arithmetic by specifying the exact operation. The resource (measurement's SPL level) and manner (fixed offset) are unambiguous.

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?

No guidance is provided on when to prefer this tool over alternatives. It does not mention related tools (e.g., align_spl, arithmetic) or when this would be a better choice. The description implies a simple offset but lacks explicit usage context or exclusions.

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