calculate_wave_properties

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

No annotations provided. The description says 'Returns missing values' but does not disclose default behavior (speed defaults to 343) or edge cases. Lack of transparency on what happens with invalid or extra inputs.

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 three sentences, front-loaded with purpose, formula, and usage hint. Concise and well-structured, though the inaccuracy detracts slightly.

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 description is incomplete: it does not explain returns, does not cover the default speed behavior, and contradicts the schema. Sibling reference is minimal. Output schema exists but not described.

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%, baseline 3, but the description introduces a non-existent parameter (wavelength) and does not clarify the default speed. It adds confusion rather than clarity.

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 tool computes wave properties using the formula c=λ·f, specifying verb+resource. However, it claims inputs include wavelength, which is not in the schema, causing slight confusion.

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 says 'any 2 of (frequency Hz, wavelength m, speed m/s)' but the schema only has frequency_hz and speed_ms, making this misleading. No explicit when-to-use or when-not-to-use guidance.

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