vocametrix_calculate_gne

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

No annotations are provided, so the description carries the full burden. It discloses the algorithm ('native Praat algorithm') and interpretation, but does not cover edge cases (e.g., invalid files), permissions, or idempotency. Adequate but not fully transparent.

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 two sentences, front-loaded with the main purpose and result, followed by interpretation and algorithm reference. No redundant information.

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?

Given the single parameter and no output schema, the description covers purpose, interpretation, and algorithm. It does not explicitly state the return format (likely a numeric value), but that is inferable. Could mention handling of invalid inputs or prerequisites.

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%, so baseline is 3. The description adds the context that the audio should be a 'sustained vowel', which is specific and not in the schema description alone. This adds meaningful guidance for parameter selection.

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 specifies the verb 'calculate', the resource 'Glottal-to-Noise Excitation (GNE) ratio', and the input 'from a sustained vowel', clearly distinguishing it from sibling tools like vocametrix_calculate_hnr or vocametrix_calculate_jitter_shimmer.

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 implies use for sustained vowels and interprets GNE values (e.g., <0.5 suggests breathiness), providing clinical context. However, it lacks explicit guidance on when to use this versus alternatives or 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.