vocametrix_generate_therapy_plan

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

No annotations provided. The description discloses asynchronous execution, ~30-120 second duration, and prerequisite steps, adding value beyond the tool name.

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?

Three sentences: core action, workflow guidance, prerequisite. No redundancy, front-loaded with key 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?

Adequately covers async pattern, time estimate, and prerequisite. Missing explicit statement about output format beyond ID, but subsequent tools handle retrieval, and no output schema exists.

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%; the description does not add new parameter details beyond the schema (e.g., 'must include patient_id' is already in schema). It provides high-level workflow context but not parameter-level semantics.

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 launches an asynchronous therapy plan generation from audio embeddings, returns a session ID, and is distinct from sibling tools like approve or get result.

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?

Explicitly says to poll status with vocametrix_get_therapy_status and retrieve result with vocametrix_get_therapy_result, plus prerequisite of extracting embeddings first.

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