vocametrix_calculate_hnr

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

With no annotations, the description carries the full burden. It explains the meaning of HNR (higher = cleaner voice) and provides a normal reference value (>20 dB for 500 Hz band). It also notes age/gender norms, which are relevant. No side effects or destructive actions are mentioned, but the tool is a read-only analysis.

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 consists of two sentences, front-loading the core purpose and adding a normal value and requirement in the second. No unnecessary information is present.

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 lacks information about the return format (e.g., a map of frequency bands to HNR values). Given no output schema, the output should be described to ensure the agent knows what to expect. While the description is adequate for a simple metric, it is incomplete without output details.

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?

The schema coverage is 100%, and the description adds value by connecting patientAge and patientGender to age- and gender-specific norms, which justifies their inclusion. It does not provide additional format details beyond the schema.

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 verb 'Calculate' and the specific metric 'multi-band Harmonics-to-Noise Ratio (HNR)' across frequency bands with norms. It distinguishes from sibling tools like vocametrix_calculate_avqi or vocametrix_calculate_cpp, which focus on different voice metrics.

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 mentions the requirement for a sustained vowel, which provides context for when to use the tool. However, it does not explicitly state when to use this tool versus alternatives, nor does it specify when not to use it.

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