Probe Voice in Original Editor

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

Description adds value beyond annotations by noting the render is bounded, temporary, and cached by fingerprint. Annotations (readOnlyHint=false, destructiveHint=false) are consistent. The transient nature and caching behavior are useful behavioral details not present in structured fields.

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?

Single sentence of 18 words, front-loaded with verb and resource. Every word adds value; no redundancy or filler.

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 existence of an output schema and moderate complexity (5 params, 1 required), the description combined with annotations covers the essential behavior. Missing details like error handling or when caching is invalid but not critical.

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 60%, and the description does not elaborate on parameters. It adds no extra meaning beyond what the schema provides (e.g., component_id, force, timeout_seconds). Baseline of 3 is appropriate since schema already documents most parameters.

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 verifies one local voice using a temporary render in the original Editor and caches the result. This specific verb+resource combination distinguishes it from sibling tools like vocaloid_host_readiness or vocaloid_analyze_wav.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, conditions, or when not to use it. Sibling tools exist (e.g., vocaloid_host_readiness) that could be confused, but no differentiation is provided.

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