calculate_wave_properties

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

No annotations provided, so the description must fully disclose behavior. It mentions the wave equation and output of 'missing values,' but does not clarify that the tool actually computes wavelength given frequency and speed (since wavelength is not an input). The default speed of 343 m/s is mentioned in the schema but not in the description. The agent cannot infer the exact behavior or constraints.

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 short and front-loaded with the purpose and formula, but it is misleading due to missing parameter. Conciseness is positive, but inaccuracy reduces its effectiveness.

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?

The tool has no annotations and an output schema not shown. The description fails to explain the actual behavior (compute wavelength from frequency and speed) and does not compensate for the missing parameter. The hint to see list_bundles is minor. Overall, the description is incomplete and inconsistent with the schema.

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?

Input schema coverage is 100%, but the description adds confusion by listing parameters (wavelength, period) that are not in the schema. It does not clarify that only frequency and speed are accepted, and that speed has a default. The formula is given but not linked to how the parameters map to it.

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 says 'Compute wave frequency, wavelength, or period from any two' but the input schema only contains 'frequency_hz' and 'speed_ms' (with a default), lacking a wavelength or period parameter. This misalignment between description and schema undermines purpose clarity; an agent cannot determine what the tool actually computes.

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 on when to use this tool versus alternatives (e.g., 'calculate_wavelength_frequency' sibling). The description implies any two inputs work, but the schema contradicts this by requiring frequency and allowing only an optional speed. No exclusions or context provided.

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