clio_update_medical_record

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions routing and scope (JWT, tenant, company), but does not disclose whether the operation is idempotent, what permissions are required, or what happens on failure or missing records.

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 short but wastes space on generic routing information that likely applies to all clio tools. The lack of front-loaded actionable content makes it inefficient for an agent to parse.

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 tool has only one parameter and no annotations, the description should at least outline the expected JSON structure or link to documentation. It fails to provide sufficient information for correct invocation, despite having an output schema (not shown).

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?

The single parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which adds minimal meaning. With 0% schema description coverage, the description should provide expected keys or structure but does not.

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 restates the tool name ('Clio connector operation `update_medical_record`') without explaining what updating a medical record entails. It fails to differentiate from sibling tools like `clio_update_medical_records_detail` or `clio_update_medical_bill`, leaving the agent without a clear verb+resource definition.

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 no guidance on when to use this tool versus alternatives. It omits prerequisites, context, and any conditions that would inform tool selection among the many clio update tools.

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