clio_update_medical_bill

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

Annotations are absent, so the description should disclose behavioral traits. It mentions routing through `/api/tools/invoke` and scope (JWT, tenant, company), but does not explain side effects, success/failure outcomes, or any constraints. Very limited transparency.

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 includes redundant routing and platform tool info that does not aid understanding. It could be more concise by removing the platform tool name and routing path, though the overall length is acceptable.

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 having an output schema, the description does not mention it or any return value. The single opaque parameter lacks detail, and no examples or required fields are provided. The tool's complexity is low but the description fails to provide sufficient context for correct invocation.

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 only parameter is a JSON string `arguments` with no schema description (0% coverage). The description repeats 'JSON string of arguments for the connector operation' without specifying expected keys, types, or structure. The agent receives no guidance on how to populate this parameter.

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 identifies the tool as updating a medical bill via a Clio connector, but it does not differentiate it from sibling tools like clio_update_medical_record or clio_update_medical_records_detail. The verb and resource are stated, but the lack of specific fields or scope limits clarity.

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, prerequisites, or context. The description focuses on routing and authentication rather than usage context.

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