vocametrix_calculate_abi

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

With no annotations provided, the description must fully disclose behavioral traits. It states the tool aggregates specific acoustic metrics but does not clarify if it is a read-only operation, whether it modifies data, or what error conditions exist. This leaves significant behavioral 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?

The description is two sentences with no redundant words. It front-loads the purpose and lists key aggregated metrics efficiently, earning its place with high information density.

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?

Despite listing many metrics, the description lacks context for interpreting the ABI (e.g., output range, clinical meaning) and does not explain return values. Among many sibling calculate tools, more detail on when to use ABI over others would improve completeness.

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 provides 100% coverage with descriptions for both 'connectedSpeechPath' and 'sustainedVowelPath'. The description mentions these inputs but does not add semantic detail beyond the schema, meeting the baseline for full schema coverage.

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 calculates the Acoustic Breathiness Index (ABI) and specifies it combines connected speech and sustained vowel. However, it does not explicitly differentiate from sibling tools like vocametrix_calculate_avqi or vocametrix_calculate_dsi, which also compute voice indices.

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 use this tool versus alternatives like AVQI or DSI. The description lists aggregated metrics but does not explain the specific context or clinical purpose that distinguishes ABI from other calculations.

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