vocametrix_get_therapy_result

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

No annotations are provided, so the description carries full burden. It describes the return content ('full therapy session with exercise plans, clinical narrative, and HTML report path'). It would benefit from stating if the tool is idempotent or what happens if called before result is ready, but overall it discloses key behavior.

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?

Two sentences front-load the purpose and the critical usage condition. Every sentence adds value with no redundancy.

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 a simple tool with one parameter and no output schema, the description covers purpose, usage condition, and return contents. It provides sufficient context for correct invocation and understanding of what it does, though more detail on the structure of the returned data would elevate it.

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?

Only one parameter with 100% schema coverage. The description adds minimal value by noting the session ID comes from vocametrix_generate_therapy_plan, which is helpful context but not essential beyond the schema itself.

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 'Retrieve the completed therapy plan result' with a specific verb and resource. It distinguishes from sibling tools like vocametrix_get_therapy_status by explicitly referencing the precondition involving that tool.

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 provides explicit guidance: 'Only call when vocametrix_get_therapy_status returns result_available = true or status = ''complete''.' This clearly tells the agent when to use this tool versus alternatives, leaving no ambiguity.

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